PINE64 - User contributions [en]

RK3399 boot sequence

2020-08-06T07:52:06Z

As400: /* Boot sequence details */

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

== Boot sequence details ==

There are two types of internal memory inside rk3399:

* 32KB BootROM - containing a small program which loads initial bootloader.It supports loading it from SPI, eMMC, SD and USB OTG in so called - maskrom mode.
* 200KB SRAM

Actual boot sequence:

1. BootROM loads U-Boot TPL into SRAM. It's job is to initialize main system RAM. 
2. Control goes back from U-Boot TPL to BootROM. 
3. BootROM loads U-Boot SPL. 
4. U-Boot SPL loads ATF and U-Boot itself into main memory. 
5. ATF runs U-Boot. 
6. U-Boot loads payload (eg. EFI binaries, grub). Direct Linux kernel load is also supported.

U-boot can boot from many sources - eMMC, SD, USB, NVME.

'''idbloader.img''' contains TPL and SPL. 
'''u-boot.itb''' contains ATF and U-Boot.

== Description ==

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

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

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

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

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

RK3399 boot sequence

2020-08-06T07:29:47Z

As400:

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

== Boot sequence details ==

There are two types of internal memory inside rk3399:

* 32KB BootROM - containing a small program which loads initial bootloader.It supports loading it from SPI, eMMC, SD and USB OTG in so called - maskrom mode.
* 200KB SRAM

Actual boot sequence:

1. BootROM loads U-Boot TPL into SRAM. It's job is to initialize main system RAM. 
2. Control goes back from U-Boot TPL to BootROM. 
3. BootROM loads U-Boot SPL. 
4. U-Boot SPL loads ATF and U-Boot itself into main memory. 
5. ATF runs U-Boot. 
6. U-Boot loads payload (eg. EFI binaries, grub). Direct Linux kernel load is also supported.

U-boot can boot from many sources - eMMC, SD, USB, NVME.

== Description ==

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

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

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

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

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

Pinebook Pro SPI

2020-02-10T19:54:06Z

As400: /* Recovering from broken SPI flashes/installs */

== 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 uboot, 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:
*Plug the Type-A end into your non-Pinebook Pro device.
*Plug the Type-C end into your Pinebook Pro.
*Remove all bootable devices from 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 rkdevelop tools. 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.

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

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.

One way or the other 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]]

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 
rkdeveloptool wl 0 zerospi 
rkdeveloptool td 
rkdeveloptool rd 
</code>

Pinebook Pro SPI

2020-02-08T20:37:52Z

As400: /* Recovering from broken SPI flashes/installs */

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

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

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.

One way or the other 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. Unscrew bottom cover. 
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
4. Locate SPI flash (number 29 on picture with Pinebook Pro internals). 
5. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode. (see picture)

[[File:Spi.png]]

Pinebook Pro SPI

2020-02-08T20:37:34Z

As400: /* Recovering from broken SPI flashes/installs */

File:Spi.png

2020-02-08T20:36:03Z

As400:

Pinebook Pro SPI

2020-02-08T20:34:24Z

As400: /* Pinebook Pro SPI */

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

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

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.

One way or the other 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. Unscrew bottom cover. 
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
4. Locate SPI flash (number 29 on picture). 
5. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode.

Pinebook Pro SPI

2020-02-08T20:34:04Z

As400:

= Pinebook Pro SPI =

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

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

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.

One way or the other 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. Unscrew bottom cover. 
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
4. Locate SPI flash (number 29 on picture). 
5. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode.

Pinebook Pro SPI

2020-02-08T20:26:25Z

As400: /* Writing to the Pinebook Pro SPI Flash */

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 rkdevelop tools. 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.

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

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.

One way or the other 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. Unscrew bottom cover. 
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
4. Locate SPI flash (number 29 on picture). 
5. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode.

Pinebook Pro SPI

2020-02-08T20:26:02Z

As400: /* Recovering Pinebook Pro SPI Flash */

== Writing to the Pinebook Pro SPI Flash ==

Placeholder text for instructions/procedure to flash the PBP SPI.

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 rkdevelop tools. 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.

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

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.

One way or the other 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. Unscrew bottom cover. 
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb. 
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb). 
4. Locate SPI flash (number 29 on picture). 
5. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode.

Pinebook Pro Hardware Accessory Compatibility

2020-01-15T16:13:45Z

As400: /* NVMe SSD drives */

This page was started in the early days when not all accessories/peripherals have been working

== NVMe SSD drives ==
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good ||
|-
| 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 ||
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || good ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || too power hungry?
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || too power hungry?
|-
| 2280 || Corsair MP300 || 120 GB || || good ||
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected
|-
| 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 ||
|-

== USB hardware ==
{| 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-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 bad, card reader bad ||
|-
|USB-C combo hub (hdmi, network, card slots, usb ports) || generic || || all bad ||
|-
|USB-C combo hub (hdmi, vga, ethernet, card slots, usb 2 & 3 || Powlaken || 05e3:0610 || USB and power delivery good, all others don't work ||
|-
|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. || 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 to HDMI adaptor || generic || || good || tested to 4k60
|-
|USB C to DP Adapter || OrxnQ || Upto 4K@60Hz || good || tested to 1080p
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|4 Port USB 3 NIC || Delock 62966 || || All good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|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 bad, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || No video. Kernel exception on connect, freezes PBP || Manjaro 2020-01-10
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|}

== Other hardware ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good
|-
|512GB SD Card || Samsung Evo Select || MB-ME512GA/AM || good
|-
|}

Pinebook Pro Hardware Accessory Compatibility

2020-01-15T16:11:10Z

As400: /* NVMe SSD drives */

This page was started in the early days when not all accessories/peripherals have been working

== NVMe SSD drives ==
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Result || Notes
|-
| 2242 || Toshiba OCZ RC 100 || 240 GB || RC100-M22242-240G || good ||
|-
| 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 ||
|-
| 2280 || Samsung 970 EVO Plus || 250 GB || MZ-V7S250BW || good ||
|-
| 2280 || Samsung 970 EVO Plus || 500 GB || MZ-V7S500 || fail || too power hungry?
|-
| 2280 || Samsung 970 EVO || 1 TB || MZ-V7E1T0BW || fail || too power hungry?
|-
| 2280 || Corsair MP300 || 120 GB || || good ||
|-
| 2280 || Silicon Power P34A60 || 256 GB || ??? || fail || Isn't detected
|-
| 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 ||

== USB hardware ==
{| 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-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 bad, card reader bad ||
|-
|USB-C combo hub (hdmi, network, card slots, usb ports) || generic || || all bad ||
|-
|USB-C combo hub (hdmi, vga, ethernet, card slots, usb 2 & 3 || Powlaken || 05e3:0610 || USB and power delivery good, all others don't work ||
|-
|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. || 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 to HDMI adaptor || generic || || good || tested to 4k60
|-
|USB C to DP Adapter || OrxnQ || Upto 4K@60Hz || good || tested to 1080p
|-
|Yubikey original || Yubico || 1050:0010 || good ||
|-
|4 Port USB 3 NIC || Delock 62966 || || All good || 4 individually controllable Gigabit Ethernet Ports. Consider using it with own power supply
|-
|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 bad, video up to 1080p. || https://forum.pine64.org/showthread.php?tid=8728
|-
|USB-C HDMI adapter (DP-alt mode) || QGeeM || || No video. Kernel exception on connect, freezes PBP || Manjaro 2020-01-10
|-
|USB-2 Fast Ethernet adapter || Realtek RTL8152 || 0bda:8152 || good ||
|}

== Other hardware ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Result
|-
|Bluetooth Mouse || HP Z5000 || E5C13AA || good
|-
|Bluetooth Mouse || Logitech Triathlon M720 || || good
|-
|Bluetooth Mouse || Logitech MX Anywhere 2 || || good
|-
|Bluetooth Mouse || Fenifox low profile || MX106-Black || good
|-
|512GB SD Card || Samsung Evo Select || MB-ME512GA/AM || good
|-
|}