PINE64 - User contributions [en]

SOEDGE

2020-11-16T20:24:16Z

Ian-S-McB: Add link to SoC product page

== Software and OS Image Downloads ==
=== SOEdge Software Release ===

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

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

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

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

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

[[File:Vivante_Acuity_SDK.jpg]]

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

== SOEdge Baseboard Features ==

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

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

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

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

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

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

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

== Other Resources ==

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

SOEDGE

2020-11-16T20:21:55Z

Ian-S-McB: Fix CPU spec link

== Software and OS Image Downloads ==
=== SOEdge Software Release ===

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

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

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

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

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

[[File:Vivante_Acuity_SDK.jpg]]

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

== SOEdge Baseboard Features ==

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

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

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

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

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

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

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

== Other Resources ==

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

Pinebook Pro Hardware Accessory Compatibility

2020-09-10T19:32:32Z

Ian-S-McB: Fix format typo in last edit

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || ||
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
|-
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING good || WARNING mine was SATA and does NOT work! Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|-
|}

== USB Networking ==

Stand-alone network devices only please, see below for combination devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB Wifi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
|-
|USB Wifi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|}

== USB Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail ||
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good ||
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested ||
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, with qemu usermode and some hacks it should be possible to use the official configuration software (runs but does not work on my setup for unrelated reasons) but it may also be able to be configured using more standard methods
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

Pinebook Pro Hardware Accessory Compatibility

2020-09-10T19:30:02Z

Ian-S-McB: Add HP EX950 NVMe drive

Please test as many things as you can find with your [[Pinebook Pro]] and share the results here. Some devices which should work don't!

= Storage =

== NVMe SSD drives ==
Note that only PCIe type M.2 drives will work. Any SATA or USB type M.2 card will NOT work.
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes || Power options Active only || Save power setting?
|-
| 2280 || Kingston A2000 || 250 GB || SA2000M8250G || good || || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: enabled by default || Yes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good || || ||
|-
| 2242 || Lexar NM520 || 256 GB || LNM520-256RBNA || good ||For some data on power use and performance, see [https://forum.pine64.org/showthread.php?tid=9029 here.] || PS 0: 3.05W PS 1: 2.44W PS 2: 2.02W || No. See [https://forum.pine64.org/showthread.php?tid=8737&pid=56481#pid56481 workaround].
|-
| 2280 || XPS SX8200 || 512 GB || ASX8200PNP-512GT-C || good || Performed [https://forum.pine64.org/showthread.php?tid=8322 these] steps for physical installation. Currently rooting from drive. || ||
|-
| 2280 || Intel 660p M.2 || 512 GB || SSDPEKNW512G8X1 || good || PS 1 (2.70W) will work without issues, even under heavy load. Recommended over PS 2, as PS 2 will incur an additional 80% performance penalty. APSTE shows enabled but drive does not support it. || PS 0: 3.50W PS 1: 2.70W PS 2: 2.00W || No
|-
| 2280 || Intel 660p M.2 || 1 TB || SSDPEKNW010T8X1 || good || || PS 0: 4.00W PS 1: 3.00W PS 2: 2.20W APSTE Disabled by default || No
|-
| 2280 || Intel 660p M.2 || 2 TB || SSDPEKNW020T8 || good || [https://forum.pine64.org/showthread.php?tid=7524&pid=49300#pid49300 Performance tests results] || ||
|-
| 2280 || Intel 760p M.2 || 128 GB || SSDPEKKW128G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W APSTE: disabled by default with 4.4 kernel (mrfixit Debian), enabled by default with 5.6 kernel (Manjaro KDE) || Yes
|-
| 2280 || Intel 760p M.2 || 256 GB || SSDPEKKW256G8 || good || Firmware Revision 004C || PS 0: 9.00W PS 1: 4.60W PS 2: 3.80W PS 3: 0.045W PS 4: 0.004W Need to use lower power. ||
|-
| 2280 || integral 256GB SSD M.2 2280 NVME || 256 GB || INSSD256GM280NM1 || usable || || PS 0: 9.00W || No
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || fail || Tested on Manjaro-ARM as root drive. Limited to PS 2 and Volatile Write Cache off gives the most stable results, but it will still hang on a hdparm test. || ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || Too power hungry? || PS 0: 6.2W PS 1: 4.3W PS 2: 2.1W ||
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || Too power hungry? || ||
|-
| 2280 || Corsair MP300 || 120 GB || CSSD-F120GBMP300 || good || || PS 0: 3.00W PS 1: 2.00W PS 2: 2.00W PS 3: 0.1W PS 4: 0.005W APSTE Disabled by default ||
|-
| 2280 || Silicon Power P34A60 || 1TB || SP001TBP34A60M28 || Usable || Power eager, but doesn't seem to use all 9W all the time, only under heavy I/O || PS 0: 9W || N/A
|-
| 2280 || Silicon Power P34A60 || 256 GB || SPCC M.2 PCIe SSD || detected || ASIN B07ZH6QR8Q "Silicon Power PCIe M.2 NVMe SSD 256GB Gen3x4" / PCIe A60 || PS 0: 6.77W PS 1: 5.71W PS 2: 5.19W APSTE Enabled by default || No
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected || ||
|-
| 2280 || Sabrent Rocket || 256 GB || SB-ROCKET-256 || good || || || No
|-
| 2242 || Sabrent Rocket Nano || 512 GB || SB-1342-512 || good* || No touchpad issues, didn't trim NVME adapter board. (*Might be too power hungry. More testing needed.) || ||
|-
| 2280 || MyDigitalSSD SBXe || 960 GB || || good || || APST enabled Power states N/A || N/A
|-
| 2280 || HP SSD EX900 || 250GB || || good || No low-power modes available || ||
| 2280 || HP SSD EX950 || 512GB || || good || Unsure about low-power modes || ||
|-
| 2280 || WD BLUE SN550 || 1TB || WDC WDS100T2B0C-00PXH0 || WARNING good || WARNING mine was SATA and does NOT work! Booted successfully from NVMe (Bionic MATE) || PS 0: 3.50W PS 1: 2.70W PS 2: 1.90W APSTE Disabled by default || N/A
|-
| 2280 || WD Blue SN500 || 500GB || WDS500G1B0C || fail || Works OK on power state 2 (2.5W), but hangs the system whenever there is intense IO (peak draw) on the drive || ||
|-
| 2242 || WD PC SN520 || 256GB || - || fail || Power LED Flashes. Nothing else happens. || ||
|-
| 2280 || WD BLACK SN750 || 250GB || WDS250G3X0C-00SJG0 || good || No touchpad issues, didn't trim NVME adapter board. || APSTE disabled by default PS 0: 5.00W PS 1: 3.50W PS 2: 3.00W||
|-
| 2280 || WD BLACK SN750 || 500GB || WDS500G3X0C-00SJG0 || good || No tp issues. had to charge battery for 20% initially. || APSTE disabled by default PS 0: 5.50W PS 1: 3.50W PS 2: 3.00W PS 3: 0.07W PS 4: 0.0025W||
|-
| 2242 || KingSpec NE-512 || 512 GB || NE512 || good || || APST enabled Power states N/A || N/A
|-
| 2230 || Kioxia BG4 256GBTB|| 256 GB || KBG40ZNS256G || good || || APST enabled by default Power states PS 0: 3.60W PS 1: 2.60W PS 2: 2.20W PS 3: 0.005W PS 4: 0.005W ||
|-
| 2280 || Patriot P300 || 256 GB || P300P256GM28US || good || Booted successfully with / on NVMe and /boot on eMMC (Armbian Buster) || APSTE disabled by default PS 0: 4.50W PS 1: 2.70W PS 2: 2.16W PS 3: 0.07W PS 4: 0.002W||
|-
| 2280 || Team Group MP33 || 128 GB || TM8FP6128G0C101 || good || || ||
|-
| 2280 || Team Group MP34 || 512 GB || TM8FP6512G0C101 || fail ||APST enabled by default and scripts do not change the power mode. Higher power consumption modes cause the PBP to crash || PS 0 5.55W PS 1 4.49W PS 2 3.97W PS 3 0.0490W PS 4 0.0018W ||No
|}

== microSD Cards ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|SD Card || Samsung Evo Select 512GB || MB-ME512GA/AM || good ||
|-
|SD Card || Samsung Evo Plus 64GB || || good || Hdparm tested 44MBps read speeds
|-
|SD Card || Sandisk Ultra 400GB || || good || Works fine as a storage extension. Mounted for pictures, etc.
|-
|}

= USB hardware =

== USB Card Readers ==

Stand-alone card readers only please, see below for combination devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 SDHC reader || Sandisk MobileMate+ || 0781:b2b3 || good ||
|-
|USB-3 SDHC/CF reader || Transcend TS-RDF8K || 8564:4000 || good ||
|-
|}

== USB Networking ==

Stand-alone network devices only please, see below for combination devices

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|-
|USB-2 Ethernet adapter || ASIX AX77882 || 0b95:7720 || good ||
|-
|USB Wifi Dongle || TP-Link TL-WN725N || 0bda:8179 || good || RTL8188EUS, Driver=rtl8188eu from MrFixit stock Debian, works better than internal Broadcom, but signal still not great, https://www.amazon.com/gp/product/B008IFXQFU/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
|-
|USB Wifi Dongle || Shenzhen Dudes Tech #8541553244 || 0bda:c811 || mixed || plug/play on stock Armbian Buster with driver rtl8821cu; could not get operating driver built on MrFixit Debian or Manjaro KDE Plasma. Works 2x+ better than internal Broadcom on Armbian. https://www.amazon.com/gp/product/B07F595V22/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
|-
|USB 3 to Gigabit Ethernet Adapter || Pluggable USB 3.0 to Ethernet Gigabit (ASIX AX88179 chipset) || 0b95:1790 || good ||
|-
|}

== USB Combination Devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C Hub || Totu 8-in-1 || 058f:8468, 2109:0817 USB3, 1a40:0801, 2109:2817 USB2, bda:8153 RTL8153 Gigabit Ethernet || Network, USB, Card Reader, Power Good, HDMI Not Working || Amazon Smile [https://smile.amazon.com/gp/product/B07FX2LW35/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1]
|-
|USB-C Hub || Delock 87721 || || Network Works, USB Works, Card Reader not tested, Power Good, HDMI Works but does not show as an extra output in X. It just mirrors the default display || Delock 87721 [https://www.delock.de/produkte/G_87721/merkmale.html?setLanguage=en]
|-
|USB-3 combo hub (network, card slots, usb ports) || generic || 05e3:0610 hub, 0bda:8153 gigE, 05e3:0743 card reader || Network good, usb ports good, card reader good ||
|-
|USB-C combo hub (network, card slots, usb ports) || generic || 05e3:0612 hub, 0bda:8153 realtek gigE || Network good, usb ports fail, card reader fail ||
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || 05e3:0626 hub || HDMI, Network, USB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg good] || Might need changing orientation or USB-C cable
|-
|4 Port USB 3 NIC || Delock 62966 || || good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|USB-C combo hub || [https://www.amazon.com/gp/product/B07XKRGQQ2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 from Amazon] || 0c76:161f 0c45:6321 2109:0813 1a40:0101 || good || Everything works: AltMode DP, Ethernet, SD card, USB-A and C, and charging using the stock Debian, and Ubuntu.
|-
|USB-C dock || i-Tec USB-C Metal Nano Dock 4K HDMI w/ LAN || 0bda:0411 hub, 0bda:8153 ethernet || mixed || plug & play with Manjaro, HDMI tested w/ fullHD only, works but only in one polarity. Sound output works, USB hub works. HDMI output may not be recognized by Plasma if dock is connected with HDMI port disconnected. NIC recognized by kernel, but untested if link actually works. USB power delivery works only in one polarity. Unfortunately HDMI works with opposite polarity than USB PD.
|-
|USB-C dock || Planet Computers Gemini USB-C hub || 0bda:0411 hub, 0bda:8153 ethernet || good || USB works, NIC recognized by kernel, but untested if link actually works. Interestingly, dmesg shows unconnected alternate mode DP, but no connector is present. It seems as if PlanetCom actually made custom version of above i-Tec device.
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|USB-C to HDMI adapter 201018 || Cable Matters || || good || Tested up to 1080p30, audio works
|-
|USB-C to HDMI adapter || Choetech HUB-H06 || || good || Advertises support for 4K@60Hz, tested up to 1080p@60Hz, worked in both Debian and Manjaro 2020-04-04
|-
|USB-C to HDMI adapter || generic || || good || Tested up to 4k60
|-
|USB-C to DP Adapter || OrxnQ || 04b4:5210 || good || Advertises support for 4K@60Hz, tested up to 1080p. Only FullHD resolutions available on Debian.
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || good || Manjaro 2020-01-25
|-
|USB-C combo hub (HDMI, network, card slots, USB ports) || generic || || fail ||
|-
|USB-C combo hub (HDMI, VGA, Ethernet, card slots, USB 2 & 3 || Powlaken || 05e3:0610 0bda:8153 || USB, Power, Ethernet and SD good, HDMI and VGA fail ||
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power Passthru || Digitus DA-70865 || || USB, Ethernet and MicroSD/SD good, video crashes System (fail). || Tested on Manjaro w/ Kernel 5.5. You have to turn the USB-C connector upside down for it to work. Video seems to be a driver issue.
|-
|USB-C Dock (HDMI, VGA, Ethernet, microSD/SD card slots, 2 USB 3 Ports, 1 USB-C Port, USB-Power pass-through) || generic || || Ethernet and MicroSD/SD good, USB fail, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C Dock (DP, HDMI, 1Gbps Ethernet, SD card slot, 2 USB 3 Ports, USB-C power in port || goFanco || || DP, Ethernet & USB good, (HDMI & SD card untested). Video tested good to 1080p || Tested on default Debian
|-
|USB-C Dock (HDMI, USB 3.0 x 2, USB-C PD Pass Thru Power Port Up to 100W, SD/TF Card Reader || Hiearcool 7-in-1 || || HDMI, USB, Power Port good, SD/TF Reader fail || Default Debian
|-
|USB-C 3.0 Multi-Port Hub (HDMI, USB 3.0 x 1, USB-C charge only) || Linden LITCAD17 || || HDMI and USB good, Power Port fail || Default Debian & ayufan Ubuntu
|-
|USB-C to DP adapter || Nekteck || 04b4:5210 || good || Shows up as "Cypress Semiconductor Corp. Billboard Device" in lsusb and dmesg output. Works in latest Manjaro (as of January 26, 2020) with no issues. Only FullHD resolutions available on Debian.
|-
|USB-C to HDMI adapter || MHL TH002 || || good || Tested at 1080p@60
|-
|USB-C combo hub (USB-C power, HDMI, 2xUSB, 1xUSB-C(no power)) || Baseus || || good ||
|-
|USB-C Travel Dock with DP ALT-MODE || Targus DOCK411-A || 0835:2a01 (BILLBOARD DEVICE) 0bda:8153 (RTL8153 GbE Adapter) || GbE: works, HDMI: works, USB3.0 port: works, VGA: unknown || HDMI@1080p@60Hz: works OK, HDMI@4K@30Hz: works but buggy. GbE is only picked up when the USB C is plugged in with one certain side facing upwards. It is not detected the other way around. (Sounds weird, but reproduced it multiple times.)
|-
|USB-C to DP adapter || MediaGearPro AC0011 || 2109:0100 (USB 2.0 BILLBOARD) || DP: works || Only 1080p@60Hz is available, 4K resolutions not possible in contrast to what the manufacturer claims.
|-
|USB-C to DP cable || Generic on ebay || || good but with issues || Had some wonky framerates when tested on a 144hz monitor, 60hz mode was actually sent as ~48hz, 120hz mode was actually sent at ~112hz and 144hz mode was actually sent at ~120hz
|-
|UGREEN Hub USB C 9 in 1 HDMI and VGA || UGREEN || || good || VGA and HDMI works but not at the same time. HDMI audio not tested. Switching between HDMI and VGA need to replug the hub.
|-
|USB-C Dock 6-in-1 HDMI || Ugreen 50771 || || HDMI: works, Ethernet: works, 3x USB: works, USB-PD: works || Tested on Manjaro 2020/03/18 Works USB-C PD Chargers provided they can do 5V3A, works with 5V3A USB-C Raspberry Pi 4 power supply (Doesn't work with 5V2A USB-C). No HDMI Audio.
|-
|USB-C to DP cable || [https://www.amazon.es/gp/product/B01N5RFAI4/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 CHOETECH V-XCP-0012BK] || || good
|-
| [https://www.apple.com/ca/shop/product/MQ4H2AM/A/thunderbolt-3-usb%E2%80%91c-cable-08-m Thunderbolt 3 (USB‑C) Cable (0.8 m)] || Apple || || Display Port Alternate Mode: Fails, USB-PD: works || Tested on Manjaro 2020/05/29 - Charges but no video
|-
|USB-C to HDMI cable || Planet Computers USB-C to HDMI cable || || fail || does not work regardless of orientation in USB slot
|-
|USB-C combo hub || Moreslan 11in1 (https://www.amazon.fr/gp/product/B08397B66G) || || good || GbE: OK, HDMI: OK, 4 usb ports: OK, Power via USB-C: OK, microSD: OK, TFT: OK, Jack: OK, VGA: Not tested; UPDATE: HDMI Display not working anymore since Manjaro release 20.08
|-
|USB-C Multiport Adapter || [https://www.wentronic.com/en/usb-ctm-multiport-adapter-hdmi-ethernet-pd-white-62105 Goobay 62105] || || Fail || GbE: OK, UBS port: OK, Power via USB-C: OK, HDMI: Does generate an image, but it jumps X pixels right from time to time (4K@30 and FHD)
|-
| USB Type-C to HDMI Adapter || Insignia NS-PU369CH-WH || 0bda:5400|| good || tested on kernel 5.5.0, video out works, audio not tested ||
|}

== USB other ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Drawing tablet || XP Pen G430s || 28bd:0913 || good || Hardware works, with qemu usermode and some hacks it should be possible to use the official configuration software (runs but does not work on my setup for unrelated reasons) but it may also be able to be configured using more standard methods
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|}

----

= Bluetooth hardware =
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good ||
|-
|Bluetooth Mouse || Kensington Expert Wireless Trackball || || good ||
|-
|Bluetooth Mouse || Logitech MX Vertical || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good ||
|-
|Bluetooth Mouse || Logitech Ultra-Thin Touch Mouse || || good || Detects battery level as "keyboard"
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good ||
|-
|Bluetooth Mouse || Logitech M535 || 910-004432 || good ||
|-
|Bluetooth Mouse || Microsoft Bluetooth Mouse || RJN-00002 || good ||
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good ||
|-
|Bluetooth Mouse || Technet || MGS479 || good ||
|-
|Bluetooth Keyboard || Logitech MX Keys || || good || Battery level is not detected over bluetooth, detected when using the logitech receiver
|-
|Bluetooth Speaker || Ivation Acoustix || || good || Use audio sink profile
|-
|Bluetooth Headphones || Sony WH-1000XM2 || || good* || Needs pulseaudio-module-bluetooth. *Recording untested.
|-
|Bluetooth Headphones || COWIN SE7 Noise Cancelling Headphones || || good || Pairs and plays audio with stock Debian OS. More detail [https://forum.pine64.org/showthread.php?tid=8192&pid=60682#pid60682 here].
|-
|USB Audio & Bluetooth Headset || Sony SBH90C || || good || Works well connected via USB Type-C and Bluetooth.
|-
|Bluetooth Headset || BlueAnt Ribbon || 7252A-RB || good || a2dp mode works, headset mode seems to work, out of box with manjaro
|-
|}

----

= Other hardware =

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result || Notes
|-
|[https://www.aliexpress.com/item/32831647303.html USB charging cable] || - || - || good || Got the cable a while back so may not be identical to current product
|-
|Printer || HP DeskJet Ink Advantage 3775 || || good* || Using hplip-gui: via USB and WiFi. *Only print function tested.
|-
|}

Pinebook Pro SPI

2020-09-01T05:32:40Z

Ian-S-McB: Shift chip diagram to right of text

The Pinebook Pro comes equipped with two non-volatile storage components, the eMMC and the SPI. The capacity of the SPI is 128MiB and it may be used in the boot process.

Boot data can be written to the SPI via two methods: either from within PBP or from a second machine connected to the PBP by USB.

= Writing to SPI from within PBP =

[https://forum.pine64.org/member.php?action=profile&uid=15527 Forum user pcm720] showed an example of writing to the SPI from within PBP in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch/Manjaro) and the <code>dd</code> command.

= Writing to SPI from a second machine =

Writing to the SPI from a second machine is more complicated than the other method, but it is the only option when troubleshooting an SPI flash gone wrong. This method works by bringing the PBP into <code>maskrom mode</code> and issuing commands on the second machine that download the flash image onto the PBP.

Upon entering <code>maskrom mode</code>, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate <code>maskrom mode</code> by logging to <code>journalctl</code>.

There are two ways to reach <code>maskrom mode</code>, but the first tends to be less reliable.

== Maskrom mode (unreliable method) ==

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in the SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next method.

== Maskrom mode (reliable method) ==

# Build and install <code>rkdeveloptool</code> (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Verify successful installation. Running <code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
# Run <code>journalctl -f</code> and keep it running. Once maskrom mode is reached it will produce additional output.
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU. The shield is held in place by a tape and micro clamps on the board. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).
# Connect your PBP with USB-C - USB-A cable to second machine (PBP on USB-C side)
# Short pins CLK and VSS (see chip diagram to the right for the names of pins). This can be done with a pair of tweezers when short on tools. [[File:Spi.png|right]]
# Press the reset button (component number 28)
# Check if there is new output from <code>journalctl</code> program.
# Check if the PBP connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>

== After entering maskrom mode ==

Now that the PBP is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin].

# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.
# Flash the new SPI binary: <code>rkdeveloptool wl 0 SPI_new.bin</code>. If successful, the output should read: <code>Write LBA from file (100%)</code>.
# Test the installation: <code>rkdeveloptool td</code>. If successful, output should read <code>Reset Device OK</code>.
# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Zeroing out the SPI ==

In case, you wrote something bad to your SPI, it's helpful to wipe away that data with zeros. To do that, you follow the same steps above to enter <code>maskrom mode</code> and then write an binary file that consists of all zeros.

# Create the binary file <code>dd if=/dev/zero of=zero.bin bs=1M count=16</code>
# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.
# Flash the new SPI binary: <code>rkdeveloptool wl 0 zero.bin</code>. If successful, the output should read: <code>Write LBA from file (100%)</code>.
# Test the installation: <code>rkdeveloptool td</code>. If successful, output should read <code>Reset Device OK</code>.
# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

Talk:Pinebook Pro SPI

2020-09-01T05:12:47Z

Ian-S-McB: /* Consolidated content, clarified some points */

== Consolidated content, clarified some points ==

After my struggle with a bad SPI flash, I wanted to give back to community the knowledge I learned, so I tidied up this article. Originally, it was a bit repetitious, jumped right into writing to SPI, and lacked some detail about what to expect if you reach <code>maskrom mode</code> Credit goes to great community members who helped me along the way: as400, phone, gnarface, and CrystalGamma - [[User:Ian-S-McB|Ian-S-McB]] ([[User talk:Ian-S-McB|talk]]) 05:11, 1 September 2020 (UTC)

Talk:Pinebook Pro SPI

2020-09-01T05:12:06Z

Ian-S-McB: Add explanation of my recent contribution

== Consolidated content, clarified some points ==

After my struggle with a bad SPI flash, I wanted to give back to community the knowledge I learned, so I tidied up this article. Originally, it was a bit repetitious, jumped right into writing to SPI, and lacked some detail about what to expect if you reach <code>maskrom mode</code> Credit goes to great community members who helped me along the way: as400, phone, gnarface, and CrystalGamma [[User:Ian-S-McB|Ian-S-McB]] ([[User talk:Ian-S-McB|talk]]) 05:11, 1 September 2020 (UTC)

Pinebook Pro SPI

2020-09-01T04:53:15Z

Ian-S-McB: Overhaul whole article

The Pinebook Pro comes equipped with two non-volatile storage components, the eMMC and the SPI. The capacity of the SPI is 128MiB and it may be used in the boot process.

Boot data can be written to the SPI via two methods: either from within PBP or from a second machine connected to the PBP by USB.

= Writing to SPI from within PBP =

[https://forum.pine64.org/member.php?action=profile&uid=15527 Forum user pcm720] showed an example of writing to the SPI from within PBP in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch/Manjaro) and the <code>dd</code> command.

= Writing to SPI from a second machine =

Writing to the SPI from a second machine is more complicated than the other method, but it is the only option when troubleshooting an SPI flash gone wrong. This method works by bringing the PBP into <code>maskrom mode</code> and issuing commands on the second machine that download the flash image onto the PBP.

Upon entering <code>maskrom mode</code>, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate <code>maskrom mode</code> by logging to <code>journalctl</code>.

There are two ways to reach <code>maskrom mode</code>, but the first tends to be less reliable.

== Maskrom mode (unreliable method) ==

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in the SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next method.

== Maskrom mode (reliable method) ==

# Build and install <code>rkdeveloptool</code> (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Verify successful installation. Running <code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
# Run <code>journalctl -f</code> and keep it running. Once maskrom mode is reached it will produce additional output.
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU. The shield is held in place by a tape and micro clamps on the board. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).
# Connect your PBP with USB-C - USB-A cable to second machine (PBP on USB-C side)
# Short pins CLK and VSS (see chip diagram below for names of pins). This can be done with a pair of tweezers when short on tools. [[File:Spi.png]]
# Press the reset button (component number 28)
# Check if there is new output from <code>journalctl</code> program.
# Check if the PBP connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>

== After entering maskrom mode ==

Now that the PBP is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin].

# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.
# Flash the new SPI binary: <code>rkdeveloptool wl 0 SPI_new.bin</code>. If successful, the output should read: <code>Write LBA from file (100%)</code>.
# Test the installation: <code>rkdeveloptool td</code>. If successful, output should read <code>Reset Device OK</code>.
# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Zeroing out the SPI ==

In case, you wrote something bad to your SPI, it's helpful to wipe away that data with zeros. To do that, you follow the same steps above to enter <code>maskrom mode</code> and then write an binary file that consists of all zeros.

# Create the binary file <code>dd if=/dev/zero of=zero.bin bs=1M count=16</code>
# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.
# Flash the new SPI binary: <code>rkdeveloptool wl 0 zero.bin</code>. If successful, the output should read: <code>Write LBA from file (100%)</code>.
# Test the installation: <code>rkdeveloptool td</code>. If successful, output should read <code>Reset Device OK</code>.
# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

Pinebook Pro SPI

2020-09-01T02:30:32Z

Ian-S-McB: Adding introduction text

The Pinebook Pro comes equipped with two non-volatile storage components, the eMMC and the SPI. The capacity of the SPI is 128MiB and it may be used in the boot process.

= Writing to the Pinebook Pro SPI =

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

= Recovering from broken SPI flashes/installs =

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

Below are the two known procedures to enter maskrom mode.

=== Simple, but unreliable maskrom mode procedure ===

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next procedure.

=== Demanding, but reliable maskrom mode procedure ===

# Compile rkdeveloptools (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (number 29 on picture with Pinebook Pro internals).
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side)
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

= Zeroing out SPI Flash =

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T01:59:07Z

Ian-S-McB: Removed unneeded heading but keep outline

= Writing to the Pinebook Pro SPI =

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

= Recovering from broken SPI flashes/installs =

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

Below are the two known procedures to enter maskrom mode.

=== Simple, but unreliable maskrom mode procedure ===

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next procedure.

=== Demanding, but reliable maskrom mode procedure ===

# Compile rkdeveloptools (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (number 29 on picture with Pinebook Pro internals).
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side)
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

= Zeroing out SPI Flash =

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T01:49:29Z

Ian-S-McB: Correct typo: one missing word

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

Below are the two known procedures to enter maskrom mode.

=== Simple, but unreliable maskrom mode procedure ===

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next procedure.

=== Demanding, but reliable maskrom mode procedure ===

# Compile rkdeveloptools (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (number 29 on picture with Pinebook Pro internals).
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side)
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T01:48:55Z

Ian-S-McB: Fix syntax for link

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

Below are the two known procedures to enter maskrom mode.

=== Simple, but unreliable maskrom mode procedure ===

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next procedure.

=== Demanding, but reliable maskrom mode procedure ===

# Compile rkdeveloptools (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. The clamps can released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (number 29 on picture with Pinebook Pro internals).
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side)
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T01:46:27Z

Ian-S-McB: Add detail about metal shield removal including a forum link with photos

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

Below are the two known procedures to enter maskrom mode.

=== Simple, but unreliable maskrom mode procedure ===

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next procedure.

=== Demanding, but reliable maskrom mode procedure ===

# Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool.
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. The clamps can released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (number 29 on picture with Pinebook Pro internals).
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side)
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T01:33:25Z

Ian-S-McB: Separate the two maskrom modes into sections and adjust phrasing

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

Below are the two known procedures to enter maskrom mode.

=== Simple, but unreliable maskrom mode procedure ===

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next procedure.

=== Demanding, but reliable maskrom mode procedure ===

# Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool.
# Unscrew bottom cover.
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (number 29 on picture with Pinebook Pro internals).
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side)
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T00:58:06Z

Ian-S-McB: Use proper list syntax

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

According to Rockchip documentation it should be accessible following below procedure:

# Press and hold recovery button. 
# Short press reset. 
# Release recovery button after about 3 seconds.

You may need to repeat these steps several times to successfully get into maskrom mode. The nature of this problem is not clear. There are two suspicions:

*the button is not working correctly or is just prone to failures.
*the problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. So if you experience such problem there is a way to overcome it. You can short the two pins by yourself.

Procedure:

# Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool. 
# Unscrew bottom cover. 
# Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
# Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
# Locate SPI flash (number 29 on picture with Pinebook Pro internals). 
# Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side). 
# Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T00:50:03Z

Ian-S-McB: Mention what signs to expect when entering maskrom mode

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

Upon entering maskrom mode, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate maskrom mode by logging to journalctl.

According to Rockchip documentation it should be accessible following below procedure:

1. Press and hold recovery button. 
2. Short press reset. 
3. Release recovery button after about 3 seconds.

You may need to repeat these steps several times to successfully get into maskrom mode. The nature of this problem is not clear. There are two suspicions:

*the button is not working correctly or is just prone to failures.
*the problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. So if you experience such problem there is a way to overcome it. You can short the two pins by yourself.

Procedure:

1. Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool. 
2. Unscrew bottom cover. 
3. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
4. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
5. Locate SPI flash (number 29 on picture with Pinebook Pro internals). 
6. Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side). 
7. Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>

Pinebook Pro SPI

2020-09-01T00:34:36Z

Ian-S-McB: Add article outline

= Pinebook Pro SPI =
== Writing to the Pinebook Pro SPI ==

'''Necessary Items:'''

1. A screwdriver 
2. USB Type-A to USB-C cable 
3. Another Computer with a USB-A 3.0 port
*''Not a requirement but if you want to boot from NVMe you need:''
4. A bootable NVMe (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system.

'''Procedure:'''

1. Build and install rkdeveloptool on your other computer, find out all the info to do that on [https://github.com/rockchip-linux/rkdeveloptool their Github.]

2. Verify correct and successful installation:
:<code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
3. On the same computer, make a directory to hold the necessary files.
:<code>mkdir ~/PBPBoot</code>

:You will need to have two files in this directory:
*The db flash helper([https://droppy.ironrobin.net/%24/JWP47 rk3399_loader_spinor_v1.15.114.bin]). This prepares the SPI for a binary.
*The U-Boot, or other bootloader binary.

'''Note: SPI binaries are built for SPI environment only. It will not work if you try putting it on your eMMC.'''

:<code>mv rk3399_loader_spinor_v1.15.114.bin ~/PBPBoot</code>
:<code>mv dhiv_SPI_uboot.bin ~/PBPBoot</code>
:<code>cd ~/PBPBoot</code>

4. Put the Pinebook Pro into maskrom mode:
*Remove all bootable devices from your Pinebook Pro.
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
5. Reboot the Pinebook Pro.
:To verify you are in maskrom mode, with your computers connected, run <code>rkdeveloptool ld</code>
:You should get an output like this: '''DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom'''
6. Flash the flash helper db file.
:<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>
:Upon success, the output should read '''Downloading bootloader succeeded.'''
7. Flash the new SPI binary.
:<code>rkdeveloptool wl 0 dhiv_SPI_uboot.bin</code>
:Successful output should read: '''Write LBA from file (100%)'''.
8. Test the installation.
:<code>rkdeveloptool td</code>
:Successful output should read '''Reset Device OK'''.
9. Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Recovering from broken SPI flashes/installs ==

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdeveloptools, especially to rewrite SPI flash or to erase it.

According to Rockchip documentation it should be accessible following below procedure:

1. Press and hold recovery button. 
2. Short press reset. 
3. Release recovery button after about 3 seconds.

You may need to repeat these steps several times to successfully get into maskrom mode. The nature of this problem is not clear. There are two suspicions:

*the button is not working correctly or is just prone to failures.
*the problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in an SPI device. But in some cases it just does nothing. So if you experience such problem there is a way to overcome it. You can short the two pins by yourself.

Procedure:

1. Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool. 
2. Unscrew bottom cover. 
3. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
4. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
5. Locate SPI flash (number 29 on picture with Pinebook Pro internals). 
6. Connect your PBP with USB-C - USB-A cable to another computer (PBP on USB-C side). 
7. Turn on PBP, short pins CLK and VSS and press reset. It should get your PBP into maskrom mode. (see picture)

[[File:Spi.png]]

== Zeroing out SPI Flash ==

On another computer:

1. Create a file filled with zeros 

<code>dd if=/dev/zero of=zerospi bs=1M count=16</code>

2. Write the file to SPI. 
<code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code> 
<code>rkdeveloptool wl 0 zerospi</code> 
<code>rkdeveloptool td</code> 
<code>rkdeveloptool rd</code>