PINE64 - User contributions [en]

User:CrystalGamma/RK3566 docs wishlist

2022-12-31T11:40:08Z

CrystalGamma:

While I am glad that better register documentation for the RK356x's memory controller can be found (compared to the RK3399), there are a few important details missing from the RK3566 TRM.

Docs that are not in any version of the RK356x TRM that I've seen, but are seemingly adequately covered by other TRMs:

* OTP block: a similar (if not same) block is included in the PX3O, and covered in its TRM
* PVTM/PVTPLL: RK3588 has docs for such blocks, but some signals (for instance 'bypass') don't seem to exist in the RK356x.

Hardware details specific to the RK356x that are not documented:

* (PMU_)SGRF: These are mostly TrustZone settings, they are essential for writing a secure monitor or boot firmware. I don't think there is anything gained by not publishing it (in fact transparency would make me much more confident in the security of the system).
* clock tree: while the register settings for muxes, dividers, and gates are described, which clock a gate or divider uses as input is not described. This makes understanding how to set the right frequency for a given piece of hardware difficult.
* DDR PHY: generally, I'm amazed at how good the documentation for the memory controller on the RK356x is. There are a couple of things where the register docs tell us to "Please reference to the chapter 9 to get more information" or similar (talking about the IP block's manual, which few people will have access to). For instance, what is the maximum VCO frequency of the PHY's PLL, and what is its reference clock (and which clock is used by the DDRC)?
* DDR scramble block: This seems like a very useful feature to have for security, but it's not documented, for either the RK356x or the RK3588.

User:CrystalGamma/RK3566 docs wishlist

2022-12-31T11:25:26Z

CrystalGamma: Created page with "While I am glad that better register documentation for the RK356x's memory controller can be found (compared to the RK3399), there are a few important details missing from the RK3566 TRM. Docs that are not in any version of the RK356x TRM that I've seen, but are seemingly adequately covered by other TRMs: * OTP block: a similar (if not same) block is included in the PX3O, and covered in its TRM * PVTM/PVTPLL: RK3588 has docs for such blocks, but some signals (for insta..."

Ox64

2022-10-08T07:18:05Z

CrystalGamma: Fix some spelling errors

[[File:Ox64_board.jpg|400px|thumb|right|The Ox64]]

The '''Ox64''' is a RISC-V based Single Board Computer powered by Bouffalo Lab BL808 C906 64-Bit RISC-V CPU, 32-Bit CPU, embedded 64MB PSRAM memory and build-on 3 radio RF (Wifi, BT, Zigbee). It provides breadboard friendly form factor, MicroSD Card slot, USB 2.0, and many other peripheral interfaces for makers to integrate with sensors and other devices.

[[File:RISC-V.png|600px|]]

== Software releases ==

=== Quick Links to the Source of OS Images Build ===

OS images are still in '''alpha build''' which are only fit for board bring up and testing purposes.

== SoC and Memory Specification ==
* Based on [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]
[[File:Bouffalo_Lab_icon.png|right]]
[[File:BL808_Block_Diagram.jpg|600px]]

=== CPU Architecture ===
* [https://www.t-head.cn/product/c906?lang=en T_head C906 480MHz 64-bit RISC-V CPU]
[[File:T-Head.png|right|200px]]
** Supports RISC-V RV64IMAFCV instruction architecture
** Five-stage single-issue sequentially executed pipeline
** Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
** Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
** jTLB that supports 128 entries
** Supports AXI 4.0 128-bit master interface
** Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
** With 80 external interrupt sources, 3 bits for configuring interrupt priority
** Supports BHT (8K) and BTB
** Compatible with RISC-V PMP, 8 configurable areas
** Supports hardware performance monitor (HPM) units

* [https://www.t-head.cn/product/e907?lang=en T_head E907 320MHz 32-bit RISC-V CPU]
** Supports RISC-V RV32IMAFCP instruction set
** Supports RISC-V 32-bit/16-bit mixed instruction set
** Supports RISC-V machine mode and user mode
** Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
** Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
** Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
** 32K instruction cache, two-way set associative structure
** 16K data cache, two-way set associative structure

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100Mbps Ethernet (optional, on expansion board)

=== Storage ===
* on-board 16Mb (2MB) or 128Mb (16MB) XSPI NOR flash memory
* microSD - supports SDHC and SDXC

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO Pins, including SPI, I2C and UART functionality. Possible I2S and GMII expansion
* Dual lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* mic (optional, on camera module)
* speaker (optional, on camera module)

== Board Information, Schematics and Certifications ==
* Baseboard Dimensions: 51mm x 21mm x 19mm x 3.5mm (Breadboard friendly)
* Input Power: 5V 0.5A microSD or USB-C port
* Schematic:
** [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
** [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
** [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]
* Certifications:
** 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.
** Not yet available

== Datasheets for Components and Peripherals ==
* Bouffalo BL808 SoC information:
** [https://files.pine64.org/doc/datasheet/ox64/BL808_Product_Brief_v1.0.pdf Bouffalo Lab BL808 SoC Product Brief]
** [https://files.pine64.org/doc/datasheet/ox64/BL808_DS_en_1.1(open).pdf Bouffalo Lab BL808 SoC Datasheet]
** [https://files.pine64.org/doc/datasheet/ox64/BL808_RM_en_1.0(open).pdf Bouffalo Lab BL808 SoC Reference Manual]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevive 16Mb XSPI-Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevive 128Mb XSPI-Flash Datasheet]
* Power Regulator information:
** [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

[[Category:Ox64]] [[Category:Bouffalo BL808]]

RK3399 boot sequence

2022-04-25T16:57:37Z

CrystalGamma: Fix headings

This article describes the boot sequence of the RK3399, the SoC on which the [[ROCKPro64]] single board computer, [[Pinebook Pro]] laptop and the [[PinePhone Pro]] are based.

== Boot ROM operation ==

After a hardware reset, the SoC's boot ROM (BROM) starts running on CPU0, one of the Cortex-A53s on the chip. This code is stored on a block of read-only memory, likely hard-wired into the chip.

It employs 5 strategies, in order, to load a bootloader from off-chip:

# loading from NOR flash on SPI1
# loading from NAND flash on SPI1
# loading from eMMC
# loading from SD on the SDMMC controller
# bringing up the OTG0 USB controller in device mode and accepting control transfers to load programs

Loading a bootloader from storage is done in 4 steps:

# Probing the boot device
# Finding the ID block
# Loading the first stage of the bootloader to main SRAM and running it
# (if the first stage returned to BROM) Loading the second stage to low DRAM and running it

=== ID block ===

The ID block is a 512-byte block at one of several well-known locations (depending on boot device type) scrambled using RC4 with a well-known key, which begins with the bytes 0x3b 8c dc fc (ciphertext; plaintext: 0x55 aa f0 0f).

In addition to the magic number, it contains (all fields little-endian):

* a flag to RC4-scramble the bootloader images too (32b at offset 8)
* offset (in 512 B-sectors) of the first bootloader stage (16b at offset 12)
* the size (in 2 KiB blocks) of the first bootloader stage (16b at offset 506)
* the size (in 2 KiB blocks) of the second bootloader stage (16b at offset 508)

These fields can be seen in U-Boot '''tools/rkcommon.c'''.

=== SPI boot ===

The boot ROM tries to probe the device on SPI1 by issuing the SPI-NOR 0x9f (Read Identification) command.

If the type and capacity bytes are all-ones or all-zeroes, probe fails.
If the first byte (manufacturer ID) is all-ones, the BROM uses NAND protocol, otherwise NOR protocol.

NOR protocol uses command 0x03 (low-frequency read without turnaround cycles) to read blocks, NAND protocol uses command 0x13.

The ID block is searched by loading the 32 bytes at the start of flash (TODO other load offsets) and testing for the magic number at any offset within those 32 bytes.

The SPI code has a bug that means that the 2 KiB blocks in which the bootloader is loaded have a stride of 4KiB, leaving the 2KiB inbetween as unused padding.

=== eMMC/SD boot ===

The boot ROM probes for eMMC on the eMMC controller using the normal MMC enumeration sequence (CMD0/1/2/3) at 375 kHz and runs the bus at 24 MHz, in 8-wide mode. The BROM does not support using the standard option for eMMC boot partitions.

SD is probed on the SDMMC (not the functionally equivalent SDIO) controller, using the normal SD enumeration sequence at 375 kHz and then runs the card at 12 MHz (TODO confirm) in 4-wide mode.

After initialization, eMMC and SD behave much the same. The ID block is searched by loading the blocks at sector 64 + 1024*n for n from 0 to 4 (inclusive) and checking for the magic number at the start of that sector. The BROM handles both byte- and block-addressed SD/MMC cards.

=== Hardware root of trust ===

The BROM theoretically supports SHA256/RSA2048 authentication with rollback protection.

The relevant data is stored in Secure eFuses: an enable flag, a SHA256 hash of the public key (which is stored on the boot medium) and a range of bits that are sequentially set for rollback protection.

In practice, the BROM does not verify the full length of the public key against the hash in eFuses, which means that it is most likely broken (expert review would be appreciated).

TOOD details

=== USB gadget boot ===

If no ID block is found on SPI, eMMC or SD, the BROM sets up the OTG0 USB controller to act as a USB high-speed (480 Mb/s) device with Vendor/Product ID of 2207:330c. In this state it supports most standard control requests, as well as 2 vendor control requests:

; 0x0471
: The code is loaded to main SRAM. When the transfer is done, it does a function call to the load address.
; 0x0472
: The code is loaded to low DRAM. When the transfer is done, USB is torn down and BROM jumps to the load address.

Transfer is performed by doing the requests on 4 KiB blocks. BROM considers the transfer complete as soon as a request supplies a block not 4096B long. (This means images a multiple of 4096 bytes long must be padded to achieve this condition.

== U-Boot boot sequence ==

Bootloaders based on U-Boot (including Tow-Boot) run in 4 stages on the RK3399:

# TPL, loaded by the BROM into main SRAM. Its [https://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/tpl-presentation.pdf job] is to initialize DRAM (main system memory). It returns to BROM. This job can alternatively be performed by proprietary Rockchip DDR blobs.
# SPL, loaded by the BROM into low DRAM. It loads the respective parts of TF-A BL31 into DRAM, main and PMU SRAM, and U-Boot proper into DRAM.
# TF-A BL31. It sets up EL2 to run U-Boot and stays resident until system shutdown.
# U-Boot proper. It can load EFI binaries (Grub, systemd-boot, …) from a variety of block devices (SD, eMMC, NVMe, USB Mass Storage, …).

For mainline-based U-Boots, these stages usually come in 2 images:

;idbloader.img
: contains TPL and SPL.
;u-boot.itb
: contains TF-A and U-Boot.

=== Load offsets ===

{{Note|This section applies to BSP U-Boot. Mainline-based U-Boots pack TF-A into '''u-boot.itb'''.}}

There are 3 sections for the boot loader. They are in order, without gap, though their is no need to use all the space in each section. 
Here are the details:
{| class="wikitable"
!Start in sectors
!Size in sectors
!Name
!Description
|-
| 64
| 16320
| IDBLoader
| SoC initialization code
|-
| 16384
| 8192
| OS loader
| Generally U-Boot
|-
| 24576
| 8192
| TrustedFirmware-A
|  
|}

=== General maintenance ===
If a new U-Boot is supplied, it is generally installed similar to this:
<pre># dd if=/boot/idbloader.img conv=notrunc seek=64 of=/dev/mmcblkX
# dd if=/boot/u-boot.itb conv=notrunc seek=16384 of=/dev/mmcblkX</pre>

=== Different devices ===
The RK3399 boots to multiple devices. Boot device selection is done in the following order, and it cannot be changed. 
If a device is blank / unused, the SoC code moves on to the next device in the list.
* SPI
* eMMC
* SD card
However, whence the user boot code runs, it can then give priority to other devices, if available.
The following devices are not directly bootable:
* NVMe
* USB 3
* WiFi
They can be made bootable by using one of the other devices as an initial bootloader. For example, several people have gotten their NVMe drives to be bootable with "/boot" and "/" on the NMVe. This either entails using the SPI or eMMC as the initial bootloader, with code to support PCIe NVMe devices.

== Grub as the target of the bootloader ==
It is possible to use Grub as the target of U-Boot. This would allow;
* Selecting a different boot device
* Choosing a partition on a boot device for booting
* Different kernels
* Changes in kernel command line options
However, at present, Grub does not support the video & keyboard of the Pinebook Pro. So, any selection is done through the serial console.

== Boot loader development ==

There are several projects that have their own versions of U-Boot, with different features. Here are some of the more common ones at present, 2020/06/14:
* Rockchip
* The original default Debian
* Manjaro
* U-Boot mainline

Bootloaders not based on U-Boot:

* coreboot runs on RK3399-based Chromebooks, it has not been ported to Pine64 boards yet.
* levinboot is a bootloader developed by CrystalGamma in the Pine64 community. It runs on RockPro64 and Pinebook Pro. Its development is on hiatus as of April 2022, but a fork porting it to the PinePhone Pro exists.

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

RK3399 boot sequence

2022-04-25T16:45:43Z

CrystalGamma: Separately document BROM behavior and U-Boot conventions

= Rockchip RK3399 boot sequence =

This article describes the boot sequence of the RK3399, the SoC on which the [[ROCKPro64]] single board computer, [[Pinebook Pro]] laptop and the [[PinePhone Pro]] are based.

== Boot ROM operation ==

After a hardware reset, the SoC's boot ROM (BROM) starts running on CPU0, one of the Cortex-A53s on the chip. This code is stored on a block of read-only memory, likely hard-wired into the chip.

It employs 5 strategies, in order, to load a bootloader from off-chip:

# loading from NOR flash on SPI1
# loading from NAND flash on SPI1
# loading from eMMC
# loading from SD on the SDMMC controller
# bringing up the OTG0 USB controller in device mode and accepting control transfers to load programs

Loading a bootloader from storage is done in 4 steps:

# Probing the boot device
# Finding the ID block
# Loading the first stage of the bootloader to main SRAM and running it
# (if the first stage returned to BROM) Loading the second stage to low DRAM and running it

=== ID block ===

The ID block is a 512-byte block at one of several well-known locations (depending on boot device type) scrambled using RC4 with a well-known key, which begins with the bytes 0x3b 8c dc fc (ciphertext; plaintext: 0x55 aa f0 0f).

In addition to the magic number, it contains (all fields little-endian):

* a flag to RC4-scramble the bootloader images too (32b at offset 8)
* offset (in 512 B-sectors) of the first bootloader stage (16b at offset 12)
* the size (in 2 KiB blocks) of the first bootloader stage (16b at offset 506)
* the size (in 2 KiB blocks) of the second bootloader stage (16b at offset 508)

These fields can be seen in U-Boot '''tools/rkcommon.c'''.

=== SPI boot ===

The boot ROM tries to probe the device on SPI1 by issuing the SPI-NOR 0x9f (Read Identification) command.

If the type and capacity bytes are all-ones or all-zeroes, probe fails.
If the first byte (manufacturer ID) is all-ones, the BROM uses NAND protocol, otherwise NOR protocol.

NOR protocol uses command 0x03 (low-frequency read without turnaround cycles) to read blocks, NAND protocol uses command 0x13.

The ID block is searched by loading the 32 bytes at the start of flash (TODO other load offsets) and testing for the magic number at any offset within those 32 bytes.

The SPI code has a bug that means that the 2 KiB blocks in which the bootloader is loaded have a stride of 4KiB, leaving the 2KiB inbetween as unused padding.

=== eMMC/SD boot ===

The boot ROM probes for eMMC on the eMMC controller using the normal MMC enumeration sequence (CMD0/1/2/3) at 375 kHz and runs the bus at 24 MHz, in 8-wide mode. The BROM does not support using the standard option for eMMC boot partitions.

SD is probed on the SDMMC (not the functionally equivalent SDIO) controller, using the normal SD enumeration sequence at 375 kHz and then runs the card at 12 MHz (TODO confirm) in 4-wide mode.

After initialization, eMMC and SD behave much the same. The ID block is searched by loading the blocks at sector 64 + 1024*n for n from 0 to 4 (inclusive) and checking for the magic number at the start of that sector. The BROM handles both byte- and block-addressed SD/MMC cards.

=== Hardware root of trust ===

The BROM theoretically supports SHA256/RSA2048 authentication with rollback protection.

The relevant data is stored in Secure eFuses: an enable flag, a SHA256 hash of the public key (which is stored on the boot medium) and a range of bits that are sequentially set for rollback protection.

In practice, the BROM does not verify the full length of the public key against the hash in eFuses, which means that it is most likely broken (expert review would be appreciated).

TOOD details

=== USB gadget boot ===

If no ID block is found on SPI, eMMC or SD, the BROM sets up the OTG0 USB controller to act as a USB high-speed (480 Mb/s) device with Vendor/Product ID of 2207:330c. In this state it supports most standard control requests, as well as 2 vendor control requests:

; 0x0471
: The code is loaded to main SRAM. When the transfer is done, it does a function call to the load address.
; 0x0472
: The code is loaded to low DRAM. When the transfer is done, USB is torn down and BROM jumps to the load address.

Transfer is performed by doing the requests on 4 KiB blocks. BROM considers the transfer complete as soon as a request supplies a block not 4096B long. (This means images a multiple of 4096 bytes long must be padded to achieve this condition.

== U-Boot boot sequence ==

Bootloaders based on U-Boot (including Tow-Boot) run in 4 stages on the RK3399:

# TPL, loaded by the BROM into main SRAM. Its [https://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/tpl-presentation.pdf job] is to initialize DRAM (main system memory). It returns to BROM. This job can alternatively be performed by proprietary Rockchip DDR blobs.
# SPL, loaded by the BROM into low DRAM. It loads the respective parts of TF-A BL31 into DRAM, main and PMU SRAM, and U-Boot proper into DRAM.
# TF-A BL31. It sets up EL2 to run U-Boot and stays resident until system shutdown.
# U-Boot proper. It can load EFI binaries (Grub, systemd-boot, …) from a variety of block devices (SD, eMMC, NVMe, USB Mass Storage, …).

For mainline-based U-Boots, these stages usually come in 2 images:

;idbloader.img
: contains TPL and SPL.
;u-boot.itb
: contains TF-A and U-Boot.

=== Load offsets ===

{{Note|This section applies to BSP U-Boot. Mainline-based U-Boots pack TF-A into '''u-boot.itb'''.}}

There are 3 sections for the boot loader. They are in order, without gap, though their is no need to use all the space in each section. 
Here are the details:
{| class="wikitable"
!Start in sectors
!Size in sectors
!Name
!Description
|-
| 64
| 16320
| IDBLoader
| SoC initialization code
|-
| 16384
| 8192
| OS loader
| Generally U-Boot
|-
| 24576
| 8192
| TrustedFirmware-A
|  
|}

== General maintenance ==
If a new U-Boot is supplied, it is generally installed similar to this:
<pre># dd if=/boot/idbloader.img conv=notrunc seek=64 of=/dev/mmcblkX
# dd if=/boot/u-boot.itb conv=notrunc seek=16384 of=/dev/mmcblkX</pre>

== Different devices ==
The RK3399 boots to multiple devices. Boot device selection is done in the following order, and it cannot be changed. 
If a device is blank / unused, the SoC code moves on to the next device in the list.
* SPI
* eMMC
* SD card
However, whence the user boot code runs, it can then give priority to other devices, if available.
The following devices are not directly bootable:
* NVMe
* USB 3
* WiFi
They can be made bootable by using one of the other devices as an initial bootloader. For example, several people have gotten their NVMe drives to be bootable with "/boot" and "/" on the NMVe. This either entails using the SPI or eMMC as the initial bootloader, with code to support PCIe NVMe devices.

== Grub as the target of the bootloader ==
It is possible to use Grub as the target of U-Boot. This would allow;
* Selecting a different boot device
* Choosing a partition on a boot device for booting
* Different kernels
* Changes in kernel command line options
However, at present, Grub does not support the video & keyboard of the Pinebook Pro. So, any selection is done through the serial console.

== Boot loader development ==

There are several projects that have their own versions of U-Boot, with different features. Here are some of the more common ones at present, 2020/06/14:
* Rockchip
* The original default Debian
* Manjaro
* U-Boot mainline

Bootloaders not based on U-Boot:

* coreboot runs on RK3399-based Chromebooks, it has not been ported to Pine64 boards yet.
* levinboot is a bootloader developed by CrystalGamma in the Pine64 community. It runs on RockPro64 and Pinebook Pro. Its development is on hiatus as of April 2022, but a fork porting it to the PinePhone Pro exists.

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

RK3399 boot sequence

2022-04-25T13:52:18Z

CrystalGamma: /* Boot sequence details */

= Rockchip RK3399 boot sequence =
This is for the Pine64 ROCKPro64 single board computer, and the Pinebook Pro laptop boot sequence details. While some of this may also apply to other RK3399 computers, that is up to the reader to make any appropriate changes.

== Boot sequence details ==

There are two types of internal memory inside RK3399 that are used during boot:

* 32 KiB BootROM - containing a small program which loads initial bootloader. It supports loading it from SPI, eMMC, SD and USB OTG in so-called maskrom mode.
* 200 KiB SRAM: 192 KiB main SRAM, 8 KiB PMU SRAM (used to resume from suspend-to-RAM)

Actual boot sequence for bootloaders derived from (mainline) U-Boot (including Tow-Boot):

# BootROM loads U-Boot TPL into SRAM. Its [https://www.denx.de/wiki/pub/U-Boot/MiniSummitELCE2013/tpl-presentation.pdf job] is to initialize DRAM (main system memory).
# Control goes back from U-Boot TPL to BootROM.
# BootROM loads U-Boot SPL into low DRAM.
# U-Boot SPL loads TF-A and U-Boot itself into DRAM, and certain parts of TF-A into main and PMU SRAM.
# Control is given to TF-A, which then runs U-Boot in EL2.
# U-Boot loads payload (eg. EFI binaries, grub). Direct Linux kernel load is also supported. U-Boot can boot from many sources - eMMC, SD, USB, NVMe.

U-Boot-based bootloaders usually come in 2 images:

* '''idbloader.img''' contains TPL and SPL.
* '''u-boot.itb''' contains TF-A and U-Boot.

== Description ==

There are 3 sections for the boot loader. They are in order, without gap, though their is no need to use all the space in each section. 
Here are the details:
{| class="wikitable"
!Start in sectors
!Size in sectors
!Name
!Description
|-
| 64
| 16320
| IDBLoader
| SoC initialization code
|-
| 16384
| 8192
| OS loader
| Generally U-Boot
|-
| 24576
| 8192
| TrustedFirmware-A
|  
|}

== General maintenance ==
If a new U-Boot is supplied, it is generally installed similar to this:
<pre># dd if=/boot/idbloader.img conv=notrunc seek=64 of=/dev/mmcblkX
# dd if=/boot/u-boot.itb conv=notrunc seek=16384 of=/dev/mmcblkX</pre>

== Different devices ==
The RK3399 boots to multiple devices. Boot device selection is done in the following order, and it cannot be changed. 
If a device is blank / unused, the SoC code moves on to the next device in the list.
* SPI
* eMMC
* SD card
However, whence the user boot code runs, it can then give priority to other devices, if available.
The following devices are not directly bootable:
* NVMe
* USB 3
* WiFi
They can be made bootable by using one of the other devices as an initial bootloader. For example, several people have gotten their NVMe drives to be bootable with "/boot" and "/" on the NMVe. This either entails using the SPI or eMMC as the initial bootloader, with code to support PCIe NVMe devices.

== Boot loader development ==
There are several projects that have their own versions of U-Boot, with different features. Here are some of the more common ones at present, 2020/06/14:
* Rockchip
* The original default Debian
* Manjaro
* U-Boot mainline

== Grub as the target of the bootloader ==
It is possible to use Grub as the target of U-Boot. This would allow;
* Selecting a different boot device
* Choosing a partition on a boot device for booting
* Different kernels
* Changes in kernel command line options
However, at present, Grub does not support the video & keyboard of the Pinebook Pro. So, any selection is done through the serial console.

[[Category:PineBook Pro]] [[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

Pinebook Pro

2022-04-14T13:17:59Z

CrystalGamma: /* eMMC information */ update device name

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

It's compact and slim dimensions are 329mm x 220mm x 12mm (WxDxH).

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 x4) 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: 1 x micro SD card reader (bootable), 1 x USB 2.0, 1 x USB 3.0, 1 x USB type C Host with DP 1.2 and power-in, PCIe x4 for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and touchpad 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 images ===
Under [[Pinebook Pro Software Release]] 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:

* [[PinebookPro_Software_Release#Manjaro ARM|Manjaro ARM]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Armbian|Armbian]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Twister OS|Twister OS]] (microSD Boot)
* [[PinebookPro_Software_Release#Fedora|Fedora]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Arch_Linux_ARM|Arch Linux]] (microSD and USB boot)
* [[PinebookPro_Software_Release#postmarketOS|Postmarket OS]] (microSD and USB boot)
* [[PinebookPro_Software_Release#Kali Linux|Kali Linux]] (microSD and USB boot)
* [[PinebookPro_Software_Release#DietPi|DietPi]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Q4OS|Q4OS]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#NetBSD|NetBSD]] (microSD and eMMC Boot)
* [[Pinebook_Pro_Software_Release#OpenBSD|OpenBSD release for ARM64]]
* [[Pinebook_Pro_Software_Release#Gentoo|Gentoo]]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and touchpad 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, touchpad 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.

{{warning|DO NOT update the keyboard firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when <code>step-1</code> is flashed, see the [https://reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread]. The keyboard IC corresponds to <code>U23</code> on the [[#Pinebook_Pro_Schematics_and_Certifications|top layer silkscreen of the main board]]. It is located under the keyboard flat flexible cable.}}

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 / privacy switch disabled, 3 blinks = WiFi disabled / privacy switch 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
| Can use tools like '''<code>lsusb</code>''' to detect camera's presence. If not detected, check privacy switch.
|}

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

The keyboard operates on firmware independent 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.

=== Basic summary of replacing keyboard ===

This guide is very basic and should be fleshed out with (better) pictures. There just isn't a list of steps anywhere else yet.

Here's what the replacement keyboard looks like:

[[File:Pinebook_Pro_new_keyboard-front.jpg|300px|Replacement keyboard (front)]]
[[File:Pinebook_Pro_new_keyboard-front.jpg|300px|Replacement keyboard (back)]]

''Step 0'': If changing from ISO keyboard to ANSI keyboard, or vice versa, be sure to have a system capable of running the firmware updater that you can access either remotely or with a USB keyboard beyond the internal keyboard, as the firmware for each is very different and keys won't work correctly. See https://forum.pine64.org/showthread.php?tid=8407 (and for NetBSD, https://forum.pine64.org/showthread.php?tid=8716).

''Step 1'': The remove back back panel.

There are 10 screws on the back that must be removed, and the back panel detached. I recommend using a PH0 bit. The speakers may remain attached via glue to the case and should be carefully pried off. When this is done, taking photos of how everything looks now can help put it all back together later.

[[File:Pinebook_Pro_keyboard-replacement-screws.jpg|300px|Remove the back panel]]

''Step 2'': Places to unscrew.

There are 3 items screwed into the keyboard frame that must be removed. There are 2 large screws for daughter board, 3 large screws and 1 small screw for mainboard, and 4 small screws for battery. Be sure to not lose them. I recommend a PH00 bit for the large screws on the daughter and main boards and a PH1 bit for the small screws on the battery and mainboard.

[[File:Pinebook_Pro_new_keyboard-back-removed.jpg|300px|Remove the back panel]]

''Step 3'': Remove the battery.

Once the battery screws are removed, it should be unplugged from the mainboard and removed. Note that there are two unconnected cables lying around, that should remain unconnected. They are used when the battery is disconnected entirely.

[[File:Pinebook_Pro_new_keyboard-zoom-mainboard.jpg.jpg|300px|Zoom on the mainboard]]
[[File:Pinebook_Pro_new_keyboard-zoom-daughterboard.jpg|300px|Zoom on the daughterboard]]

''Step 4'': Unplug the ribbon cables.

NOTE: you should remove the M.2 adapter board now if you have one installed. See elsewhere in this wiki for instructions on how to install/remove that piece.

There are several ribbon cables. To remove, flip up the tab and gentle pull the ribbon out.

* One cable runs from the mainboard to the daughterboard underneath the battery. Detach from both ends. With the battery removed, detach from keyboard shell, and set aside for the new keyboard shell.
* One cable runs between the touchpad and the mainboard. Detach from both ends, and also set aside.
* One cable runs between the keyboard and the mainboard. This one remains attached to the keyboard and only needs to be detached from the mainboard.
* One cable from the LCD attaches near the lid hinge. It should be just unplugged.

''Step 5'': Detach microphone, speakers, and antenna.

[[File:Pinebook_Pro_microphone_removed.jpg|300px|thumb|right|One of the Pinebook Pro microphones after removal]]

The speakers, microphone, and antenna don't have to be detached from the mainboard, but they need to be detached from the keyboard shell. The microphones are held in place by tape, and the speakers have sticky sides. The speakers are found obviously, but the microphones (two of) can be found between the battery and the hinge area. Each microphone can be carefully pulled/wedged out of its position by a small screwdriver or pick. The antenna, similar to the microphones, is found near the hinge area and to the top left of the battery.

''Step 6'': Remove mainboard and daughterboard.

At this point, the mainboard and daughterboards should be removed. When unscrewed (see Step 2) they should pull out fairly easily. Put them aside (including microphones and speakers if left attached.)

[[File:Pinebook_Pro_new_keyboard-all-boards-removed.jpg|300px|All boards removed]]

''Step 7'': Detach the LCD panel.

Step 2 didn't tell you, there are 6 more screws to remove here, 3 for each of the hinges. I recommend a PH1 bit for these screws. Unscrew these and the LCD panel will be able to be removed. You may have to jiggle or move the hinges for this. When detached, be sure to place the LCD panel such that the display is protected.

[[File:Pinebook_Pro_new_keyboard-detached-display.jpg|300px|Display detached]]
[[File:Pinebook_Pro_new_keyboard-detached-display2.jpg|300px|Display detached (front)]]

''Step 8'': Try Not To Break Your Touchpad, or, How I Learned To Love Things That Bend

'''NOTE This section really feels like you're going to break something.'''

The touchpad is glued to the keyboard shell and it's glued well. There are two places it is glued to. If you can, only the middle must be force-detached. You will think you're going to break it. Gently apply increasing force until the glue begins to detach (you will hear a crackle as it comes off), and continue very slowly until the whole thing is detached. This may take minutes due to that feeling you're going to break it.

I found it helpful to lift the top left plastic bit on the keyboard to unstick that portion of the touchpad, then push on the top left portion of the touchpad to unstick the rest of the touchpad.

[[File:Pinebook_Pro_new_keyboard-touchpad1.jpg|300px|Unmouting the touchpad]]
[[File:Pinebook_Pro_new_keyboard-touchpad2.jpg|300px|Unmouting the touchpad]]
[[File:Pinebook_Pro_new_keyboard-touchpad3.jpg|300px|Unmouting the touchpad]]

''Step 9'': Over the hill, touchpad goes into new shell.

In the new keyboard shell put the touchpad back where it was, hopefully the glue will remain sufficiently attached. If there is a glue issue, this guide unfortunately has no advice currently.

[[File:Pinebook_Pro_new_keyboard-install-touchpad.jpg|300px|Install the touchpad]]

''Step 10'': Reattach the LCD panel.

The LCD panel should slot back into the keyboard frame, the same way it came out. If the hinges were moved, they should be *very* *gently* closed such that the LCD panel and keyboard closed like normal for the remaining steps.

''Step 11'': Tape it out.

Move any tape from the old keyboard shell to the new one. These items protect the mainboard and daughterboard, and keep various wires in their right place. Some are grey and some are black. For tape that holds the speakers, microhones, or their cables in place, do not reattach yet.

''Step 12'': Board install.

Install the mainboard, the daughtboard, and their connecting ribbon cable. Be sure to put the boards in place, 2 large flat screws for the daughterboard, 3 large flat screws and one small screw for the mainboard, before attempting to place the ribbon.

''Step 13'': Microphone, speaker, and antenna install.

Reattach the microphones, antenna, and speakers to their respective areas, making sure that both are properly oriented - the speaker "out" faces up, and the microphone cables as connected must face up (these are opposite directions.)

''Step 14'': Reattach other ribbon cables.

NOTE: this would be a good time to attach/install the M.2 adapter board if that is desired. See elsewhere in this wiki for those instructions.

The LCD panel, keyboard and touchpad ribbon cables should be reattached. Make sure the flap is open, insert the ribbon into the slot (a portion of the cable will disappear), and push the flap down. The cable should not be easy to pull out.

''Step 15'': Reattach the battery, and final re-tape.

The battery should be installed with the 4 screws holding it in place, and the connector attached to the mainboard. Be sure to keep the two other cables remain unconnected. Ensure all wires and other tapes are held in place.

''Step 16'': Reattach the back panel.

Put the back panel back on, and reattach the 10 screws.

''Step 17'': If you changed from ISO to ANSI or from ANSI to ISO, you'll need to update your firmware now. See the links in Step 0 above.

== Touchpad (trackpad) ==
Documentation for the touchpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]]. It is the only component of the Pinebook Pro held in place with strong adhesive tape. Here are some of its features:

* 2 actuating buttons.

* multi-touch functionality.

* A matte finish that your finger can slide along easily.

* A reasonable size (96mm × 64mm; diagonal: 115.378mm or 4.542”).

=== Troubleshooting ===

If you are having trouble using 2 fingers to scroll or emulate the click of a mouse's right-button, then try these solutions:

* Update the firmware.

* Keep your 2 fingers spread apart rather than close together.

* Individual programs might need to be configured specially.

:* For smooth scrolling and gestures under X-Windows, ''Firefox'' should be launched with with the following environment variable assignment:

::: <code>MOZ_USE_XINPUT2=1</code>

* Experiment with other settings, via [[#X-Windows Configuration|X-Windows Configuration]] or some other system preferences; for example, you could disable double-finger scrolling, and instead enable scrolling by sliding one finger along the edge of the touchpad.

=== Firmware ===
The touchpad controller is connected to the keyboard controller. All touchpad events go through the keyboard controller and it's software, then to the keyboard controller's USB port. Note that the touchpad does have separate firmware, (which has to be written through the keyboard controller). The touchpad vendor’s firmware binary can be flashed from userspace using the following open source command-line utility:

* Kamil Trzciński’s [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater pinebook-pro-keyboard-updater].

Naturally, forks have begun to appear:

* Jack Humbert’s [https://github.com/jackhumbert/pinebook-pro-keyboard-updater fork]

* Dragan Simic’s [https://github.com/dragan-simic/pinebook-pro-keyboard-updater fork]. This one has recently delivered a much improved firmware from the vendor, which greatly improves the control of the cursor (see this [https://forum.pine64.org/showthread.php?tid=14531 thread] for discussion); before installing this update, consider resetting to the defaults any configuration of your touchpad.

'''Every Pinebook Pro produced before September 2021 should have its keyboard and touchpad firmware updated.'''

{{warning| DO NOT update the touchpad firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when <code>step-1</code> is flashed. See [//old.reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread]. The keyboard IC corresponds to <code>U23</code> on the [[#Pinebook_Pro_Schematics_and_Certifications|top layer silkscreen of the main board]]. It is located under the keyboard flat flexible cable.}}

Before updating ''any'' firmware, your Pinebook Pro should be either fully charged or, preferably, running from mains. This utility will be writing data to chips on the keyboard and touchpad, so a loss of power during any stage of the update can result in irrecoverable damage to your touchpad 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. To install these dependencies, newer Pinebook Pro models that come with Manjaro will require a different command.

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:

* Connection to WiFi (for getting dependencies).

* Your Pinebook Pro fully charged or running from mains power.

* An external USB keyboard & mouse (or access to the Pinebook Pro via SSH. Please note that for some configurations, the SSH service might not be available without first having logged in once; in this case, you will definitely want at least an external keyboard).

==== 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 poweroff # do not use 'reboot'
</pre>

Step 2 (after booting)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 iso
sudo poweroff # do not use 'reboot'
</pre>

==== ANSI Model ====

{{Hint| Note: Running step 1 on the ANSI keyboard model will make the keyboard and touchpad inaccessible until step 2 is run, 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 poweroff # do not use 'reboot'
</pre>

Step 2 (after booting)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 ansi
sudo poweroff # do not use '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 may have shipped with English UK as the default language; you can change it to English US if desired.

==== Revised Firmware ====

In addition, you might consider using revised firmware data; this is one final step that should not require a reboot:

Step 3: '''ISO''' (after booting)
<pre>
sudo ./updater flash-kb firmware/default_iso.hex
</pre>

Step 3: '''ANSI''' (after booting)
<pre>
sudo ./updater flash-kb firmware/default_ansi.hex
</pre>

=== X-Windows Configuration ===
''Before making adjustments, consider updating the firmware; reset your adjustments before updating the firmware, so that your adjustments do not interfere with new functionality.''

Some forum members have found that an adjustment to X-Windows will allow finer motion in the touchpad. If you use the '''Synaptic''' mouse/touchpad 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 TapButton1=1
synclient TapButton2=3
synclient TapButton3=2
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.
 

<code>TabButton</code> allows to just tab the touchpad instead of physically pressing it down (to get this click noise).

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

Some users may encounter an issue with the mouse jumping when typing when using libinput driver (has not been test with synaptic) due to their hand hitting the touchpad which can be fixed by updating the xorg settings to disable it while typing. One can disable the touchpad while typing by setting the below option in the xorg config simliar to the previou example.

<pre>
Option "DisableWhileTyping" "on"
</pre>

The setting can be verified by using the xinput command to first list the devices and then listing the properties for the Touchpad device. Exact commands to check this have been omitted for save of brevity. If DisableWhileTyping is shown enabled but does not appear to be working the issue may be due to the fact that the keyboard is connected to a USB bus which causes it to be seen as a external keyboard. To resolve this one can add the config below which sets the keyboard to internal to ensure the DisableWhileTyping works properly.

You will need to edit <code>/etc/libinput/local-overrides.quirks</code> and add the following lines:
<pre>
[Serial Keyboards]
MatchUdevType=keyboard
MatchBus=usb
AttrKeyboardIntegration=internal
</pre>

Once X11 is restarted the new setting should now take effect and you will no longer be able to use the touchpad while typing which will mostly eliminate the mouse jumping issue.

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

# The red LED next to the barrel port indicates charging, in three ways. First, it will illuminate steadily when either the factory power supply or a USB Type-C charger is connected to the Pinebook Pro, and the battery is getting charged. Second, if the battery is at 100%, the LED will remain turned off regardless of the connected power input; however, this is [https://forum.pine64.org/showthread.php?tid=10899 rather rarely achieved]. Third, this LED will flash at 0.5 Hz if there are any problems that prevent charging, such as the battery becoming too hot.
# The power indicator LED, above the keyboard, supports three different colors: green, amber and red. It is also capable of flashing to indicate eMMC activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).
# The green NumLock LED, above the keyboard.
# The green CapsLock LED, above the keyboard.

The NumLock and CapsLock LEDs serve their usual purposes on a keyboard, but they also have a secondary function. When the privacy switches get activated they blink to confirm that the switch has been activated.

== Webcam ==
{{Hint| You can use Cheese to test the Camera functionality}}
* Streaming video resolutions supported, (uncompressed):
** 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

== 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 changing the [[Pinebook_Pro#Privacy_Switches|privacy switches]]. If the switches are in the correct place and microphone input isn't working you can run <code>alsamixer</code> 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 one with input. Additionally you may want to modify ADC PGA to get the levels to where you want them. If that still hasn't fixed it you may want to check that the microphone connector is plugged in (see the section [[#Technical Reference|Technical Reference]]).

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

To disable Bluetooth under Linux once:

sudo rfkill block bluetooth

To confirm if Bluetooth under Linux is disabled:

rfkill

To disable Bluetooth on boot (note: for distributions such as Manjaro XFCE see the step below):

sudo systemctl enable rfkill-block@bluetooth

To disable Bluetooth on certain distributions, such as Manjaro XFCE, right click on the Bluetooth panel icon, select plugins, then PowerManager, then configuration and then deselect the auto power on option

== LCD Panel ==
* Model: BOE NV140FHM-N49
* 14.0" (35.56 cm) diagonal size
* 1920x1080 resolution
* 60 Hz refresh rate
* IPS technology
* 1000:1 contrast
* 250 nit brightness
* 63% sRGB coverage
* 6-bit color
* 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:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter. Swapping the tx and rx around from this also works and is more traditional. See the official [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pine64 document].]]

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 [[Pinebook_Pro#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.3 V interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3 V and 5 V variants) to avoid damage to the CPU. Older version of the serial console cable sold by Pine64 uses wrong voltage level and should not be used; see [https://forum.pine64.org/showthread.php?tid=9367 this forum thread] for further information. Recent version of the same cable uses the right voltage level.

Insert the USB plug of the cable into an open USB port on the machine which will monitor, ensuring that the audio jack of the serial cable is be fully inserted into the Pinebook Pro audio port. 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>

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.

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

=== 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 touchpad interference. New orders as of Feb. 22nd, 2020 will be the updated adapter.

This is the link to the Pinebook Pro accessories in the store: [[https://pine64.com/?v=0446c16e2e66]]

Actual installation instructions are a work in progress. Unofficial instructions for installing V2-2019-1107 can be found [https://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 [https://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 ===

Under [[Pinebook_Service_Step_by_Step_Guides|Service Guides for Pinebook]] you can find instructions guides concerning disassembly of:

* The installation process on Pinebook Pro similar to 14" Pinebook
* 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]] for details.

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.

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

With Mesa 20.2 there is no longer much reason to use this over the standard mesa package, and applications may occasionally break with mesa-git.

[https://docs.mesa3d.org/bugs.html Reporting bugs] to the Mesa project will help make sure any problems are quickly fixed.

=== OpenGL 3.3 support ===
By default, with the current state of the Panfrost GPU driver, the Pinebook Pro supports OpenGL 2.1 and OpenGL ES 3.0. If you want to use OpenGL 3.3, 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="gl3"</pre>
Then save the file, entering your password when prompted, and reboot the system. When you check your GPU capabilities, it should report OpenGL 3.3 and applications that rely on it should function properly. Note that GL 3.3 support is incomplete and some rendering features do not work yet, notably geometry shaders.

=== Install Anbox on Pinebook Pro Manjaro 20.10 ===
[https://www.youtube.com/watch?v=EU8_Q11dATs Youtube video on installing Anbox on Pienbook Pro Manjaro Build 20.10 by LivingLinux]

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

==== Debian ====
* Backup and edit the U-Boot configuration file:

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

Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.

* Update the U-Boot configuration:

u-boot-update

* Test and verify you get what you think you should be seeing.

==== Manjaro ====
* Backup and edit the U-Boot configuration file:

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

* 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. One such method that someone used successfully, is: <blockquote><code>echo "Xft.dpi: 150" >> ~/.Xresources</code></blockquote>Change the 150 as desired to get the size adjustment you want.
 
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 =

Do not panic if something goes wrong or in an unexpected way. Instead, stop and consider carefully how to undo something, or how to redo it. This particularly applies when flashing a new operating system, or flashing new firmware to the keyboard or touchpad. If everything fails, consider reporting the issue on the forums, with as many relevant details as available.

Please, have a look at the [[Pinebook Pro Troubleshooting Guide]], which details a number of issues you may encounter.

= Hardware/Accessory Compatibility =
Please contribute to the [[Pinebook Pro Hardware Accessory Compatibility|hardware/accessory compatibility page]], which lists the status of hardware tested with the Pinebook Pro. Available hardware categories include the following:

* [[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 =
== Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

[[File:Hinges_cover_removed_1.jpeg|300px|thumb|right|Hinge area of the Pinebook Pro lid with the cover removed]]
[[File:Hinges_cover_removed_2.jpeg|300px|thumb|right|Close-up of a Pinebook Pro lid hinge]]

There are a few '''mandatory''' precautions to be taken:

* 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.
* When removing the back cover plate, *do not, under any circumstances, slide your fingertips between the metal shell and the plastic frame!* The back cover plate edges are sharp, and when combined with the pressure and movement generated from, specifically, attempting to slide the tips of your fingers along the bottom edge of the plate along the lid-hinge, they *will* slice open the tips of your fingers like a knife.
* When removing the back cover plate, use care to avoid damaging the speakers. They can be stuck to the back cover with double-sided tape, and the thin wires are very delicate. Newer Pinebook Pro laptops (as of the May 2021 batch, and perhaps earlier) seem to lack the double-sided tape to the rear cover, instead opting for tape or glue that makes them stick to the front cover. Nevertheless, be gentle when removing the back cover.

[[File:PinebookProScrewGuide.png|400px|thumb|right|Pinebook Pro external screws (this particular unit has suffered damage on screw (4)L)]]

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. There are four (4) short screws along the front edge, and six (6) long screws along the 3 remaining sides. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis. The aluminum case is held on only by screws. There are no plastic snaps, and the shell should pull away without any effort. If you experience any resistance at all stop and ensure all ten (10) screws are accounted for.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. Before replacing the aluminum back-plate, ensure that the speakers are properly seated by pressing gently on the hard plastic edge of the speaker module. Slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the touchpad 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 4 short screws.

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 (which may be caused by the aforementioned misseating of the speakers), 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, re-open the machine and check for misseated components.

A basic 3D model to print replacement standoffs for the back cover screws is [https://www.thingiverse.com/thing:4226648 available on Thingiverse], until the official drawings or 3D models are made available.

====Display Disassembly====
It is not recommended to adjust the position of the lid when the bottom cover is removed, because the bottom cover provides structural strength, so the lid should be open fully as the first step, before starting any disassembly of the laptop. After opening the lid, remove the bottom cover by following the instruction found in the section above. Alternatively, you can keep the lid closed and remove the screws that hold the hinges to the main laptop body, as described in [[Pinebook Service Step by Step Guides]].

Parts of the hinge mechanism, as well as the screws that hold the hinges to the lid, are hidden behind an elongated plactic U-shaped cover that snaps in place using latches. Use a dedicated plastic prying tool or a guitar pick to gently pry the cover and remove it, starting from the outer edge. Once you pry the cover to a certain extent, it should be possible to remove it fully using only your hands. The U-shaped cover is rather sturdy, but still be careful not to break or bend it.

There are two small screws hidden underneath the two small rubber nubs on the upper part of the screen bezel, so first gently remove the nubs and then remove the screws. The screen bezel is held in place with a combination of latches and some adhesive tape, which is there to prevent dust ingress. The adhesive isn't very strong, and the bezel is capable of flexing back into shape after being twisted to a certain extent. There is more adhesive on the bottom part of the screen bezel, so be more careful while prying that section apart. Use the same prying tool that you used for the U-shaped cover, and work it around the outer edges of the screen bezel.

== 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 x4 slot for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Touchpad 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 || Touchpad
|-
! 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/ u-boot] 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 OSes 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. Note that the enable/disable label on the silkscreen is incorrect on some board revisions (known bad on v2.1).

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.mmc >/sys/bus/platform/drivers/sdhci-arasan/unbind
echo fe330000.mmc >/sys/bus/platform/drivers/sdhci-arasan/bind
</pre>

(Note: with the device trees coming with older kernels (Linux < 5.11), the device name may be fe330000.sdhci instead of fe330000.mmc)

== Case Dimensions and Data ==
* 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 1.1, 2.5 GT/s per lane
** Note that due to errata, PCIe is limited to Gen1. See [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/rockchip/rk3399.dtsi?id=712fa1777207c2f2703a6eb618a9699099cbe37b this commit].
* Four PCIe lanes, which can not be bifurcated, but can be used with one- or two-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.5 W continuous, 8.25 W 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:
** [https://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:
** [https://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:
** [https://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:
** [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Case:
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.pdf AutoCAD PDF File ]
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.ai AutoCAD AI File ]
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.dwg AutoCAD DWG File ]
* Pinebook Pro Certifications:
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet v2.1]
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.4%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.4, part 1]
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.3, part 1] and [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part2.pdf part 2]
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet v0.8]
* LPDDR4 SDRAM (366-pin BGA):
** [https://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 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://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (updated)]
* Wireless and Bluetooth information:
** [https://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio codec:
** [http://www.everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec Datasheet]
* LCD panel:
** [https://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* USB-related information:
** Internal USB 2.0 hub: [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub Datasheet]
** USB Type-C Controller: [https://www.onsemi.com/pub/Collateral/FUSB302-D.PDF ON Semiconductor FUSB302 Datasheet]
* Touchpad information:
** [https://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf PineBook Pro Touchpad Specification]
* Keyboard information:
** [https://wiki.pine64.org/images/b/b0/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD camera sensor:
** [https://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification (in Chinese)]
** [https://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Datasheet]
* Battery-related information:
** Battery charging IC: [https://www.ti.com/lit/ds/symlink/bq24171.pdf?ts=1607068456825&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FBQ24171 Texas Instruments BQ24171 Datasheet]
** Battery monitoring IC: [https://cdn.datasheetspdf.com/pdf-down/C/W/2/CW2015-Cellwise.pdf Cellwise CW2015 Datasheet]
** [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification]
* 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 FH26-35S-0.3SHW flat flex connector (compatible, not OEM)]

== 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]
* [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]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* [[Pinebook Pro/Freepascal and Lazarus IDE on Manjaro|Freepascal and Lazarus IDE on Pinebook Pro]]

[[Category:PineBook Pro]]
[[Category:Rockchip RK3399]]

Pinebook Pro

2021-10-14T16:32:00Z

CrystalGamma: /* eMMC information */ Add note that the silkscreen label for eMMC enable/disable is wrong on some versions, notably 2.1.

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

It's compact and slim dimensions are 329mm x 220mm x 12mm (WxDxH).

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 x4) 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: 1 x micro SD card reader (bootable), 1 x USB 2.0, 1 x USB 3.0, 1 x USB type C Host with DP 1.2 and power-in, PCIe x4 for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and touchpad 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 images ===
Under [[Pinebook Pro Software Release]] 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:

* [[PinebookPro_Software_Release#Manjaro ARM|Manjaro ARM]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Armbian|Armbian]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Twister OS|Twister OS]] (microSD Boot)
* [[PinebookPro_Software_Release#Fedora|Fedora]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Arch_Linux_ARM|Arch Linux]] (microSD and USB boot)
* [[PinebookPro_Software_Release#postmarketOS|Postmarket OS]] (microSD and USB boot)
* [[PinebookPro_Software_Release#Kali Linux|Kali Linux]] (microSD and USB boot)
* [[PinebookPro_Software_Release#DietPi|DietPi]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#Q4OS|Q4OS]] (microSD and eMMC Boot)
* [[PinebookPro_Software_Release#NetBSD|NetBSD]] (microSD and eMMC Boot)
* [[Pinebook_Pro_Software_Release#OpenBSD|OpenBSD release for ARM64]]
* [[Pinebook_Pro_Software_Release#Gentoo|Gentoo]]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and touchpad 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, touchpad 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.

{{warning|DO NOT update the keyboard firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when <code>step-1</code> is flashed, see the [https://reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread]. The keyboard IC corresponds to <code>U23</code> on the [[#Pinebook_Pro_Schematics_and_Certifications|top layer silkscreen of the main board]]. It is located under the keyboard flat flexible cable.}}

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 / privacy switch disabled, 3 blinks = WiFi disabled / privacy switch 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
| Can use tools like '''<code>lsusb</code>''' to detect camera's presence. If not detected, check privacy switch.
|}

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

The keyboard operates on firmware independent 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.

=== Basic summary of replacing keyboard ===

This guide is very basic and should be fleshed out with pictures. There just isn't a list of steps anywhere else yet.

''Step 0'': If changing from ISO keyboard to ANSI keyboard, or vice versa, be sure to have a system capable of running the firmware updater that you can access either remotely or with a USB keyboard beyond the internal keyboard, as the firmware for each is very different and keys won't work correctly. See https://forum.pine64.org/showthread.php?tid=8407 (and for NetBSD, https://forum.pine64.org/showthread.php?tid=8716).

''Step 1'': The remove back back panel.

There are 10 screws on the back that must be removed, and the back panel detached. The speakers may remain attached via glue to the case and should be carefully pried off. When this is done, taking photos of how everything looks now can help put it all back together later.

''Step 2'': Places to unscrew.

There are 3 items screwed into the keyboard frame that must be removed. There are 2 large screws for daughter board, 3 large screws and 1 small screw for mainboard, and 4 screws for battery. Be sure to not lose them.

''Step 3'': Remove the battery.

Once the battery screws are removed, it should be unplugged from the mainboard and removed. Note that there are two unconnected cables lying around, that should remain unconnected. They are used when the battery is disconnected entirely.

''Step 4'': Unplug the ribbon cables.

There are several ribbon cables. To remove, flip up the tab and gentle pull the ribbon out.

* One cable runs from the mainboard to the daughterboard underneath the battery. Detach from both ends. With the battery removed, detach from keyboard shell, and set aside for the new keyboard shell.
* One cable runs between the touchpad and the mainboard. Detach from both ends, and also set aside.
* One cable runs between the keyboard and the mainboard. This one remains attached to the keyboard and only needs to be detached from the mainboard.
* One cable from the LCD attaches near the lid hinge. It should be just unplugged.

''Step 5'': Detach microphone and speakers.

[[File:Pinebook_Pro_microphone_removed.jpg|300px|thumb|right|One of the Pinebook Pro microphones after removal]]

The speakers and microphone don't have to be detached from the mainboard, but they need to be detached from the keyboard shell. The microphones are held in place by tape, and the speakers have sticky sides. The speakers are found obviously, but the microphones (two of) can be found between the battery and the hinge area. Each microphone can be carefully pulled/wedged out of its position by a small screwdriver or pick.

''Step 6'': Remove mainboard and daughterboard.

At this point, the mainboard and daughterboards should be removed. When unscrewed (see Step 2) they should pull out fairly easily. Put them aside (including microphones and speakers if left attached.)

''Step 7'': Detach the LCD panel.

Step 2 didn't tell you, there are 6 more screws to remove here, 3 for each of the hinges. Unscrew these and the LCD panel will be able to be removed. You may have to jiggle or move the hinges for this. When detached, be sure to place the LCD panel such that the display is protected.

''Step 8'': Try Not To Break Your Touchpad, or, How I Learned To Love Things That Bend

'''NOTE This section really feels like you're going to break something.'''

The touchpad is glued to the keyboard shell and it's glued well. There are two places it is glued to. If you can, only the middle must be force-detached. You will think you're going to break it. Gently apply increasing force until the glue begins to detach (you will hear a crackle as it comes off), and continue very slowly until the whole thing is detached. This may take minutes due to that feeling you're going to break it.

''Step 9'': Over the hill, touchpad goes into new shell.

In the new keyboard shell put the touchpad back where it was, hopefully the glue will remain sufficiently attached. If there is a glue issue, this guide unfortunately has no advice currently.

''Step 10'': Reattach the LCD panel.

The LCD panel should slot back into the keyboard frame, the same way it came out. If the hinges were moved, they should be *very* *gently* closed such that the LCD panel and keyboard closed like normal for the remaining steps.

''Step 11'': Tape it out.

Move any tape from the old keyboard shell to the new one. These items protect the mainboard and daughterboard, and keep various wires in their right place. Some are grey and some are black. For tape that holds the speakers, microhones, or their cables in place, do not reattach yet.

''Step 12'': Board install.

Install the mainboard, the daughtboard, and their connecting ribbon cable. Be sure to put the boards in place, 2 large flat screws for the daughterboard, 3 large flat screws and one small screw for the mainboard, before attempting to place the ribbon.

''Step 13'': Microphone and speaker install.

Reattached the microphones and speakers to their respective areas, making sure that both are properly oriented - the speaker "out" faces up, and the microphone cables as connected must face up (these are opposite directions.)

''Step 14'': Reattach other ribbon cables.

The LCD panel, keyboard and touchpad ribbon cables should be reattached. Make sure the flap is open, insert the ribbon into the slot (a portion of the cable will disappear), and push the flap down. The cable should not be easy to pull out.

''Step 15'': Reattach the battery, and final re-tape.

The battery should be installed with the 4 screws holding it in place, and the connector attached to the mainboard. Be sure to keep the two other cables remain unconnected. Ensure all wires and other tapes are held in place.

''Step 16'': Reattach the back panel.

Put the back panel back on, and reattach the 10 screws.

''Step 17'': If you changed from ISO to ANSI or from ANSI to ISO, you'll need to update your firmware now. See the links in Step 0 above.

== Touchpad (trackpad) ==
Documentation for the touchpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]]. It is the only component of the Pinebook Pro held in place with strong adhesive tape. Here are some of its features:

* 2 actuating buttons.

* multi-touch functionality.

* A matte finish that your finger can slide along easily.

* A reasonable size (96mm × 64mm; diagonal: 115.378mm or 4.542”).

=== Troubleshooting ===

If you are having trouble using 2 fingers to scroll or emulate the click of a mouse's right-button, then try these solutions:

* Update the firmware.

* Keep your 2 fingers spread apart rather than close together.

* Individual programs might need to be configured specially.

:* For smooth scrolling and gestures under X-Windows, ''Firefox'' should be launched with with the following environment variable assignment:

::: <code>MOZ_USE_XINPUT2=1</code>

* Experiment with other settings, via [[#X-Windows Configuration|X-Windows Configuration]] or some other system preferences; for example, you could disable double-finger scrolling, and instead enable scrolling by sliding one finger along the edge of the touchpad.

=== Firmware ===
The touchpad controller is connected to the keyboard controller. All touchpad events go through the keyboard controller and it's software, then to the keyboard controller's USB port. Note that the touchpad does have separate firmware, (which has to be written through the keyboard controller). The touchpad vendor’s firmware binary can be flashed from userspace using the following open source command-line utility:

* Kamil Trzciński’s [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater pinebook-pro-keyboard-updater].

Naturally, forks have begun to appear:

* Jack Humbert’s [https://github.com/jackhumbert/pinebook-pro-keyboard-updater fork]

* Dragan Simic’s [https://github.com/dragan-simic/pinebook-pro-keyboard-updater fork]. This one has recently delivered a much improved firmware from the vendor, which greatly improves the control of the cursor (see this [https://forum.pine64.org/showthread.php?tid=14531 thread] for discussion); before installing this update, consider resetting to the defaults any configuration of your touchpad.

'''Every Pinebook Pro produced before September 2021 should have its keyboard and touchpad firmware updated.'''

{{warning| DO NOT update the touchpad firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a '''SH61F83''' instead of a '''SH68F83'''. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when <code>step-1</code> is flashed. See [//old.reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread]. The keyboard IC corresponds to <code>U23</code> on the [[#Pinebook_Pro_Schematics_and_Certifications|top layer silkscreen of the main board]]. It is located under the keyboard flat flexible cable.}}

Before updating ''any'' firmware, your Pinebook Pro should be either fully charged or, preferably, running from mains. This utility will be writing data to chips on the keyboard and touchpad, so a loss of power during any stage of the update can result in irrecoverable damage to your touchpad 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. To install these dependencies, newer Pinebook Pro models that come with Manjaro will require a different command.

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:

* Connection to WiFi (for getting dependencies).

* Your Pinebook Pro fully charged or running from mains power.

* An external USB keyboard & mouse (or access to the Pinebook Pro via SSH. Please note that for some configurations, the SSH service might not be available without first having logged in once; in this case, you will definitely want at least an external keyboard).

==== 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 poweroff # do not use 'reboot'
</pre>

Step 2 (after booting)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 iso
sudo poweroff # do not use 'reboot'
</pre>

==== ANSI Model ====

{{Hint| Note: Running step 1 on the ANSI keyboard model will make the keyboard and touchpad 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 poweroff # do not use 'reboot'
</pre>

Step 2 (after booting)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 ansi
sudo poweroff # do not use '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 may have shipped with English UK as the default language; you can change it to English US if desired.

==== Revised Firmware ====

In addition, you might consider using revised firmware data; this is one final step that should not require a reboot:

Step 3: '''ISO''' (after booting)
<pre>
sudo ./updater flash-kb firmware/default_iso.hex
</pre>

Step 3: '''ANSI''' (after booting)
<pre>
sudo ./updater flash-kb firmware/default_ansi.hex
</pre>

=== X-Windows Configuration ===
''Before making adjustments, consider updating the firmware; reset your adjustments before updating the firmware, so that your adjustments do not interfere with new functionality.''

Some forum members have found that an adjustment to X-Windows will allow finer motion in the touchpad. If you use the '''Synaptic''' mouse/touchpad 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 TapButton1=1
synclient TapButton2=3
synclient TapButton3=2
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.
 

<code>TabButton</code> allows to just tab the touchpad instead of physically pressing it down (to get this click noise).

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

Some users may encounter an issue with the mouse jumping when typing when using libinput driver (has not been test with synaptic) due to their hand hitting the touchpad which can be fixed by updating the xorg settings to disable it while typing. One can disable the touchpad while typing by setting the below option in the xorg config simliar to the previou example.

<pre>
Option "DisableWhileTyping" "on"
</pre>

The setting can be verified by using the xinput command to first list the devices and then listing the properties for the Touchpad device. Exact commands to check this have been omitted for save of brevity. If DisableWhileTyping is shown enabled but does not appear to be working the issue may be due to the fact that the keyboard is connected to a USB bus which causes it to be seen as a external keyboard. To resolve this one can add the config below which sets the keyboard to internal to ensure the DisableWhileTyping works properly.

You will need to edit <code>/etc/libinput/local-overrides.quirks</code> and add the following lines:
<pre>
[Serial Keyboards]
MatchUdevType=keyboard
MatchBus=usb
AttrKeyboardIntegration=internal
</pre>

Once X11 is restarted the new setting should now take effect and you will no longer be able to use the touchpad while typing which will mostly eliminate the mouse jumping issue.

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

# The red LED next to the barrel port indicates charging, in three ways. First, it will illuminate steadily when either the factory power supply or a USB Type-C charger is connected to the Pinebook Pro, and the battery is getting charged. Second, if the battery is at 100%, the LED will remain turned off regardless of the connected power input; however, this is [https://forum.pine64.org/showthread.php?tid=10899 rather rarely achieved]. Third, this LED will flash at 0.5 Hz if there are any problems that prevent charging, such as the battery becoming too hot.
# The power indicator LED, above the keyboard, supports three different colors: green, amber and red. It is also capable of flashing to indicate eMMC activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).
# The green NumLock LED, above the keyboard.
# The green CapsLock LED, above the keyboard.

The NumLock and CapsLock LEDs serve their usual purposes on a keyboard, but they also have a secondary function. When the privacy switches get activated they blink to confirm that the switch has been activated.

== Webcam ==
{{Hint| You can use Cheese to test the Camera functionality}}
* Streaming video resolutions supported, (uncompressed):
** 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

== 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 changing the [[Pinebook_Pro#Privacy_Switches|privacy switches]]. If the switches are in the correct place and microphone input isn't working you can run <code>alsamixer</code> 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 one with input. Additionally you may want to modify ADC PGA to get the levels to where you want them. If that still hasn't fixed it you may want to check that the microphone connector is plugged in (see the section [[#Technical Reference|Technical Reference]]).

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

To disable Bluetooth under Linux once:

sudo rfkill block bluetooth

To confirm if Bluetooth under Linux is disabled:

rfkill

To disable Bluetooth on boot (note: for distributions such as Manjaro XFCE see the step below):

sudo systemctl enable rfkill-block@bluetooth

To disable Bluetooth on certain distributions, such as Manjaro XFCE, right click on the Bluetooth panel icon, select plugins, then PowerManager, then configuration and then deselect the auto power on option

== LCD Panel ==
* Model: BOE NV140FHM-N49
* 14.0" (35.56 cm) diagonal size
* 1920x1080 resolution
* 60 Hz refresh rate
* IPS technology
* 1000:1 contrast
* 250 nit brightness
* 63% sRGB coverage
* 6-bit color
* 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:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter. Swapping the tx and rx around from this also works and is more traditional. See the official [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pine64 document].]]

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 [[Pinebook_Pro#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.3 V interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3 V and 5 V variants) to avoid damage to the CPU. Older version of the serial console cable sold by Pine64 uses wrong voltage level and should not be used; see [https://forum.pine64.org/showthread.php?tid=9367 this forum thread] for further information. Recent version of the same cable uses the right voltage level.

Insert the USB plug of the cable into an open USB port on the machine which will monitor, ensuring that the audio jack of the serial cable is be fully inserted into the Pinebook Pro audio port. 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>

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.

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in PineBook Pro.

=== 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 touchpad interference. New orders as of Feb. 22nd, 2020 will be the updated adapter.

This is the link to the Pinebook Pro accessories in the store: [[https://pine64.com/?v=0446c16e2e66]]

Actual installation instructions are a work in progress. Unofficial instructions for installing V2-2019-1107 can be found [https://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 [https://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 ===

Under [[Pinebook_Service_Step_by_Step_Guides|Service Guides for Pinebook]] you can find instructions guides concerning disassembly of:

* The installation process on Pinebook Pro similar to 14" Pinebook
* 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]] for details.

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.

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

With Mesa 20.2 there is no longer much reason to use this over the standard mesa package, and applications may occasionally break with mesa-git.

[https://docs.mesa3d.org/bugs.html Reporting bugs] to the Mesa project will help make sure any problems are quickly fixed.

=== OpenGL 3.3 support ===
By default, with the current state of the Panfrost GPU driver, the Pinebook Pro supports OpenGL 2.1 and OpenGL ES 3.0. If you want to use OpenGL 3.3, 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="gl3"</pre>
Then save the file, entering your password when prompted, and reboot the system. When you check your GPU capabilities, it should report OpenGL 3.3 and applications that rely on it should function properly. Note that GL 3.3 support is incomplete and some rendering features do not work yet, notably geometry shaders.

=== Install Anbox on Pinebook Pro Manjaro 20.10 ===
[https://www.youtube.com/watch?v=EU8_Q11dATs Youtube video on installing Anbox on Pienbook Pro Manjaro Build 20.10 by LivingLinux]

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

==== Debian ====
* Backup and edit the U-Boot configuration file:

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

Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.

* Update the U-Boot configuration:

u-boot-update

* Test and verify you get what you think you should be seeing.

==== Manjaro ====
* Backup and edit the U-Boot configuration file:

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

* 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. One such method that someone used successfully, is: <blockquote><code>echo "Xft.dpi: 150" >> ~/.Xresources</code></blockquote>Change the 150 as desired to get the size adjustment you want.
 
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 =

Do not to panic if something goes wrong or in an unexpected way. Instead, stop and consider carefully how to undo something, or how to redo it. This particularly applies when flashing a new operating system, or flashing new firmware to the keyboard or touchpad. If everything fails, consider reporting the issue on the forums, with as many relevant details as available.

Please, have a look at the [[Pinebook Pro Troubleshooting Guide]], which details a number of issues you may encounter.

= Hardware/Accessory Compatibility =
Please contribute to the [[Pinebook Pro Hardware Accessory Compatibility|hardware/accessory compatibility page]], which lists the status of hardware tested with the Pinebook Pro. Available hardware categories include the following:

* [[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 =
== Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

There are a few '''mandatory''' precautions to be taken:

* 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.
* When removing the back cover plate, *do not, under any circumstances, slide your fingertips between the metal shell and the plastic frame!* The back cover plate edges are sharp, and when combined with the pressure and movement generated from, specifically, attempting to slide the tips of your fingers along the bottom edge of the plate along the lid-hinge, they *will* slice open the tips of your fingers like a knife.
* When removing the back cover plate, use care to avoid damaging the speakers. They can be stuck to the back cover with double-sided tape, and the thin wires are very delicate. Newer Pinebook Pro laptops (as of the May 2021 batch, and perhaps earlier) seem to lack the double-sided tape to the rear cover, instead opting for tape or glue that makes them stick to the front cover. Nevertheless, be gentle when removing the back cover.

[[File:PinebookProScrewGuide.png|400px|thumb|right|Pinebook Pro external screws (this particular unit has suffered damage on screw (4)L)]]

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. There are four (4) short screws along the front edge, and six (6) long screws along the 3 remaining sides. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis. The aluminum case is held on only by screws. There are no plastic snaps, and the shell should pull away without any effort. If you experience any resistance at all stop and ensure all ten (10) screws are accounted for.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. Before replacing the aluminum back-plate, ensure that the speakers are properly seated by pressing gently on the hard plastic edge of the speaker module. Slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the touchpad 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 4 short screws.

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 (which may be caused by the aforementioned misseating of the speakers), 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, re-open the machine and check for misseated components.

A basic 3D model to print replacement standoffs for the back cover screws is [https://www.thingiverse.com/thing:4226648 available on Thingiverse], until the official drawings or 3D models are made available.

== 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 x4 slot for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Touchpad 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 || Touchpad
|-
! 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/ u-boot] 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 OSes 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. Note that the enable/disable label on the silkscreen is incorrect on some board revisions (known bad on v2.1).

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>

== Case Dimensions and Data ==
* 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.0, 5 GT/s per lane
* Four PCIe lanes, which can not be bifurcated, but can be used with one- or two-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.5 W continuous, 8.25 W 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:
** [https://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:
** [https://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:
** [https://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:
** [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Case:
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.pdf AutoCAD PDF File ]
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.ai AutoCAD AI File ]
** [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.dwg AutoCAD DWG File ]
* Pinebook Pro Certifications:
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]
** [https://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet v2.1]
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.4%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.4, part 1]
** [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.3, part 1] and [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part2.pdf part 2]
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet v0.8]
* LPDDR4 SDRAM (366-pin BGA):
** [https://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 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://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (updated)]
* Wireless and Bluetooth information:
** [https://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio codec:
** [http://www.everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec Datasheet]
* LCD panel:
** [https://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* USB-related information:
** Internal USB 2.0 hub: [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub Datasheet]
** USB Type-C Controller: [https://www.onsemi.com/pub/Collateral/FUSB302-D.PDF ON Semiconductor FUSB302 Datasheet]
* Touchpad information:
** [https://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf PineBook Pro Touchpad Specification]
* Keyboard information:
** [https://wiki.pine64.org/images/b/b0/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD camera sensor:
** [https://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification (in Chinese)]
** [https://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Datasheet]
* Battery-related information:
** Battery charging IC: [https://www.ti.com/lit/ds/symlink/bq24171.pdf?ts=1607068456825&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FBQ24171 Texas Instruments BQ24171 Datasheet]
** Battery monitoring IC: [https://cdn.datasheetspdf.com/pdf-down/C/W/2/CW2015-Cellwise.pdf Cellwise CW2015 Datasheet]
** [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification]
* 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 FH26-35S-0.3SHW flat flex connector (compatible, not OEM)]

== 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]
* [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]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* [[Pinebook Pro/Freepascal and Lazarus IDE on Manjaro|Freepascal and Lazarus IDE on Pinebook Pro]]

[[Category:PineBook Pro]]
[[Category:Rockchip RK3399]]

Quartz64

2021-02-17T12:34:43Z

CrystalGamma: /* Android 11 SDK */

The Quartz64 is the most recent Single Board Computer offering from Pine64, scheduled for release in 2021. It is powered by a Rockchip RK3566 Quad-Core ARM Cortex A55 64-Bit Processor with a MALI G-52 GPU.

Key features include a PCIe x2 open ended slot (model A) or m.2 (model B), the use of LPDDR4 RAM.

The Quartz64 is equipped with 2GB, 4GB or 8GB 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 A Host, 3x USB 2.0 Host, Gigabit Ethernet, GPIO Bus, MiPi DSI interface, eink interface (Model A), eDP interface (model A), touch Panel interface (model A), 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 Linux (Ubuntu, Debian, Arch), BSD, and Android.

== Software and OS Image Downloads ==

* TBD

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core Cortex-A55@1.8GHz]

* Quad-core ARM Cortex-A55 CPU
* AArch32 for full backward compatibility with Armv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Include VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache, 32KB L1 data cache
* 512KB unified system L3 cache
* TrustZone technology support

=== Graphic Process Unit GPU Capability ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Support OpenGL ES 1.1, 2.0, and 3.2
* Support Vulkan 1.0 and 1.1
* Support OpenCL 2.0 Full Profile
* Support 1600Mpix/s fill rate when 800MHz clock frequency
* Support 38.4GLOPs when 800MHz clock frequency

=== Neural Process Unit NPU Capability ===
* Neural network acceleration engine with processing performance up to 0.8 TOPS
* Support integer 8, integer 16 convolution operation
* Support deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory Variants: 2GB - 8GB LPDDR4.
* SPI Flash: 128Mbit / 16MByte

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n/ac with Bluetooth 5.0 (optional on model A, build in on model B)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 ports on model B, 3 ports on model A USB 2.0 Host port, 1 USB 3.0 Host port
* native SATA 2.0 Port (only on model A, share with USB 3.0 host port)
* optional eMMC module from 16GB up to 128GB

=== Expansion Ports ===
* eDP - 4 lanes of 2.7Gbps, up to 2560x1600@60Hz (only on model A)
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1440P on model A, 2 lanes MiPi, up to 1080p on model B
* CSI - CMOS Camera Interface, 4 lanes MiPi up to 8 mega pixel on model A, 2 lanes MiPi up to 5 mega pixel on model B
* TP - Touch Panel Port, SPI with interrupt on model A
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input on model A
* Wifi/BT Module Header - SDIO 3.0 and UART on model A, build in Wifi/BT Module on model B
* 2x20 pins "Pi2" GPIO Header on model B, 2x10 pins GPO header on model A
* PCIe 2x open ended slot on model A, m.2 slot on model B

== Quartz64 board Information, Schematics, and Certifications ==
* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 12V @ 3A 5.5mmOD/2.1mmID Barrel DC Jack connector

* Quartz64 Model "A" SBC Schematic and PCB Board Resource:
** [https://files.pine64.org/doc/quartz64/Quartz64_model-A_schematic_v1.0_20201124.pdf Quartz64 Model "A" SBC Schematic ver 1.0 20201124 PDF file]
** [https://files.pine64.org/doc/quartz64/Quartz64_model-A_V1.0_connector_placement.pdf Quartz64 Model "A" SBC PCB Connector placement PDF file]

* Model "B" Baseboard Dimensions: 85mm x 56mm x 18.8mm
* Input Power: DC 5V @ 3A 3.5mmOD/1.35mmID Barrel DC Jack connector

* Quartz64 Model "B" SBC Schematic and PCB Board Resource:
** Quartz64 Model "B" SBC Schematic not yet available
** [https://files.pine64.org/doc/quartz64/Quartz64%20model-B%20PCB%20placement.pdf Quartz64 Model "B" SBC PCB Connector placement PDF file]

* Certification:
** Not yet available

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]
* LPDDR4 (200 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-754-V3_ES103TC1%20Specification%20V3.0(Signed)-20190702.pdf Eink 10.3" 1872x1404 ES103TC1 Flex Panel Specification]
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf Eink 10.3" 1872x1404 ES103TC1 Glass Panel Specification]
* 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]
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet]]
* 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]

== Android SDK ==

=== Android 11 SDK ===
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 77c2ff57ea3372fb04da7fb49e17d12b
** File Size: 79.00GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

== Other Resources ==

[[Category:Quartz64]]

File:Rk35-blobs.tar.gz

2021-02-17T12:33:09Z

CrystalGamma: The directory rk/rkbin/bin/rk35 extracted from the Quartz64#Android SDK hosted at http://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz, uploaded, so that devs that only want a booting system without all the Android stuff can avoid downloading the 80GB SDK blob.

== Summary ==
The directory rk/rkbin/bin/rk35 extracted from the [[Quartz64#Android SDK]] hosted at [[http://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz]], uploaded, so that devs that only want a booting system without all the Android stuff can avoid downloading the 80GB SDK blob.

User:CrystalGamma/The State of (my) PBP

2019-12-31T21:26:45Z

CrystalGamma:

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[ROCKPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

The brightness (and, probably, suspend) keys need a small hwdb rule to work: [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb]

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration) still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Personal'''-authenticated networks like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/The State of (my) PBP

2019-12-31T17:10:01Z

CrystalGamma: /* What doesn't work */

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[ROCKPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration) still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Personal'''-authenticated networks like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/The State of (my) PBP

2019-12-31T16:54:35Z

CrystalGamma: /* What doesn't work */

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[ROCKPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Personal'''-authenticated networks like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/The State of (my) PBP

2019-12-31T16:54:08Z

CrystalGamma: /* What works */

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[ROCKPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Personal'''-authenticated like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/PBP Review

2019-12-31T16:52:11Z

CrystalGamma: CrystalGamma moved page User:CrystalGamma/PBP Review to User:CrystalGamma/The State of (my) PBP

#REDIRECT [[User:CrystalGamma/The State of (my) PBP]]

User:CrystalGamma/The State of (my) PBP

2019-12-31T16:52:11Z

CrystalGamma: CrystalGamma moved page User:CrystalGamma/PBP Review to User:CrystalGamma/The State of (my) PBP

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[RockPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Personal'''-authenticated like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/The State of (my) PBP

2019-12-31T16:50:32Z

CrystalGamma: /* What doesn't work */

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[RockPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Personal'''-authenticated like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/The State of (my) PBP

2019-12-31T16:49:57Z

CrystalGamma:

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[RockPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.

The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Enterprise'''-authenticated like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.

User:CrystalGamma/The State of (my) PBP

2019-12-31T15:51:43Z

CrystalGamma: Created page with "This article is supposed to give an overview of my experience with the Pinebook Pro as of 2019-12-31. It is not supposed to be a comprehensive or neutral review of the mac..."

This article is supposed to give an overview of my experience with the [[Pinebook Pro]] as of 2019-12-31.
It is not supposed to be a comprehensive or neutral review of the machine, but merely an experience report. I will probably update this page when something major changes (if I remember).

== What works ==
Booting with upstream U-Boot using the [[RockPro64]] defconfig works. (Though I've worked around the default DTB name by arranging the DTB directory to give the PBP device tree as <code>rockchip/rk3399-rockpro64.dtb</code>)
Booting with the mainline-based Manjaro kernel works.
The following works with the relevant firmware installed:
* DisplayPort Alt-Mode (dptx.bin)
* WiFi

== What doesn't work ==
This list includes various stuff that I've haven't gotten to work yet, even if it is technically possible already.

Panfrost: accelerated graphics leads to crashes in plasmashell, and I didn't have time to go deeper with debugging it because I wanted to make the PBP my main computer by the end of the year and updating mesa in NixOS is a bitch. Plasma with software rendering (i. e. whatever setup you get with <code>opengl.enable = false;</code> in the NixOS configuration still works more smoothly and with a hell of a lot more battery time than my ThinkPad X200, which my PBP replaces.

Suspend: suspend (to RAM) support isn't patched all the way through the Manjaro kernel and upstream ATF (and whatever other involved party) yet, so it will not be able to resume successfully.

WiFi doesn't work with my dorm network yet. My primary lead is to some coordination problem between userspace, kernel/driver and firmware as to which side should implement what part of 802.1X. As soon as I get my USB3A-to-Ethernet adapter, this will be less of a problem for me. Note that normal '''WPA2 Enterprise'''-authenticated like my mom's home WiFi '''do work'''.

USB-C connector reversing: both USB-C accessories I've tried have some functionality only working with the connector in a particular orientation. This is apparently because the SoC Type-C PHY needs to be instructed to swap signal, but this doesn't seem to work yet.

Keyboard/Touchpad: I was met with some initial problems with the keyboard not working when touching the touchpad. This was '''fixed in a KB/TP firmware update'''. Palm rejection could still be improved though.

Audio output: even with the UART/Headphone switch set appropriately, I get no sound on the Headphones, and the speakers are silent, too. For me this only matters when I'm on the go, since I have a USB audio device I usually use because I also use a capacitive microphone which needs 48V phantom power. This still needs to be fixed because I have no other device to play music for me during train rides (until I get a PinePhone at least).

Video en/decoding: the RK3399 provides a "Hantro" VPU used for en/decoding various video formats more efficiently and a raster-graphics accelerator (RGA) for blitting while potentially converting pixel formats. While the kernel exposes MPEG-2 and VP8 decoding as V4L2 memory-to-memory devices, stock ffmpeg and its libraries used in mpv, VLC and friends don't make use of that yet, making video playback rather CPU-costly.

Fast boot: my current system takes some 15–20s from pressing the power button to enabling the power LED (and a few more seconds to bring up the display). This is apparently because mainline U-Boot clocks the eMMC (and potentially the CPUs too) much lower than needed; I will probably side-step this entirely at some point by placing TPL and SPL in SPI flash, together with a FIT image of Linux with a (probably) Petitboot userspace, to implement a boot menu.

Brightness (and, eventually, suspend) keys: these need a special hwdb entry apparently. Nothing I can't do, I just didn't get around to figuring out how to do it on NixOS yet. The suspend key is useless as long as suspend doesn't work, and brightness I can change using the GUI or <code>/sys</code> if necessary, so it's low priority.

Logo + Arrow key combinations: I haven't gone deeper with this, but it seems the logo key cannot be used in combinations with the arrow keys (at least, without also pressing Fn, making it Logo + Home/End/PgUp/PgDn) which makes the default Plasma window tiling shortcuts not work.

== Flaws of the PBP, Hopes and Dreams for the next generation of Pinebooks ==
The ''case integrity around the hinges'' seems marginal. While I've personally not experienced any fractures yet, I've seen pictures of it happening, and always having to re-screw the bottom plates before opening the lid (as written on the inside of the case) is a bit annoying. While I'm not expecting miracles for a product in the PBP price range, some confidence that my laptop will not fracture from opening and closing it would be great.

This ties into the next wish for the next generation of Pine64 laptops: a power button that can be used with the lid closed, e. g. on the side of the case. I will be using the PBP a lot as a computer driving an external 4K display while connected to various hardware on the desk, so being able to boot with the lid closed would be useful, and being able to boot the system while flipped over with the bottom case open for access to the insides would have been much appreciated especially in the early days of bringing up the system.

My next wish concerns the keyboard: while the (in my case, ISO) keyboard has a pretty good typing experience so far for how thin it has to be to fit in the case, I am constantly noticing it has a distinct lack of auxiliary keys: navigation keys like Home/End/PgDn/PgUp and the editing keys Insert/Delete are only accessible via Fn combinations, and there are no Next Track/Previous Track/Play/Pause/Stop multimedia keys at all. On my desktop keyboard I actually map the latter to the former in combinations with the (right) logo key, but this is super awkward (and certainly not usable with a single hand) with the built-in keyboard. My wish is for at least the Home/End/PgUp/PgDn/Ins/Del group to get dedicated keys in the next generation, be it using seven columns (ThinkPad-style) or as an additional column to the right of the main keyboard.