PINE64 - User contributions [en]

ROCKPro64 Hardware compatibility

2023-09-25T07:16:14Z

ChriChri:

Hardware accessory compatibility for the [[ROCKPro64]]. Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

== Hardware compatibility ==
=== PCIe devices ===
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes || Tester
|-
| NIC || Intel I350 Dual Port || || Mainline-5.4 || style="background:PaleGreen;" | good || SR-IOV fails
|-
| NIC || Intel I350 Quad Port || || || ? ||
|-
| NIC || Intel X520 Dual Port || 8086:10fb || Mainline-5.6 || style="background:PaleGreen;" | good || SR-IOV fails
|-
| NIC || Intel X550-T2 Dual Port || 8086:1563 || 5.15.0-trunk-arm64 (Debian) || style="background:PaleGreen;" | good || netperf throughput in FW mode, 20 streams: between 4136-6613mb/s across use cases.
|-
| NIC || Intel 82571EB Dual Port (HP NC360T) || || Mainline-5.6 || style="background:#F99;" | crash || kernel crash on boot
|-
| NIC || Intel 82575EB Dual Port (AOC-SG-I2) || || Mainline-5.10 || style="background:#F99;" | crash || kernel crash on boot
|-
| NIC || Intel 82575/82576 || 8086:1521 || OpenWrt 21.02-rc1 ; 5.4.111-1 || style="background:PaleGreen;" | good ||opkg: kmod-igb ; [https://wiki.pine64.org/wiki/ROCKPro64_Software_Release#OpenWrt_21.02 OpenWrt 21.02-rc1] 5.4.111-1 ; ~92.8 KB ; Kernel modules for Intel(R) 82575/82576 PCI-Express Gigabit Ethernet adapters.
|-
| NIC || Aquantia 10GBps AQC107 || 1d6a:07b1 || Mainline 5.16 || style="background:PaleGreen;" | good || Works perfectly out of the box.
|-
| GPU || nVidia GTX-645 || || Mainline-5.4 || style="background:#F99;" | crash || BAR size too small, triggers PCIe error handling bug
|-
| PCIe Switch || PCIE-EUX1-04 Ver.002 || || Mainline-5.4 || style="background:PaleGreen;" | good ||
|-
| SATA Controller || ASM1062 4-Port || || Mainline-5.6 || style="background:PaleGreen;" | good || tested only with one disk attached
|-hw
| SATA Controller || ASM1062 (rev 02) 4-Port ||1d87:0100|| Ayufan-4.4.190 || style="background:PaleGreen;" | good || tested with four disks, 3 in raid 5
|-
| SATA Controller || IOCrest (Same as Syba?) SI-PEX40063 4-port, Marvell 88SE9235 chip || 1b4b:9235 || Debian unstable 5.7, 5.8 || style="background:PaleGreen;" | good || Tested with two disks. SATA errors occurred with a WD Red drive in a cheap enclosure; resolved by connecting the same drive directly to the card.
|-
| SATA Controller || Ziyituod SATA Card ASM 1062+1093 6-Port || 1b21:0625 || Mainline-4.4 (armbian) || style="background:PaleGreen;" | good || tested with 6 disks ||
|-
| SATA Controller || BEYMEI RAID 4-Port, Marvell 88SE9230 chip || 1b4b:9230 || Ayufan-5.6.0-1137 || style="background:PaleGreen;" | good || Tested with 3 disks in RAID 5. I added pci=nomsi to /boot/extlinux/extlinux.conf kernel parameters and an udev rule before the disks were recognized: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x1b4b", ATTR{device}=="0x9230", RUN+="/bin/bash -c 'echo %k > /sys/bus/pci/drivers/ahci/bind'"
|-
| SATA Controller || BEYIMEI SATA Card 6-Port, ASM1166 chip || || 5.10.0-16-arm64 (Debian) || style="background:PaleGreen;" | good || Tested with 4 disks. Built 2 separate software RAID-1 arrays without errors. Performance seems good enough for a NAS on gigabit LAN.
|-
| SATA Controller || PCE8SAT-A02 VER006S 2 Lanes, 8-Port, ASM1166 chip Odd because chip got only 6 ports?|| 1b21:1166 || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:#F99;" | unstable || Tested with 3 disks in SW-RAID 5. After 10 hours of burn in test one disk dropped from system *and* RAID. Hotplug does not work. || [[User:JPT|JPT]]
|-
| SATA Controller || BEYIMEI SATA Card 2-Port, ASM1062 chip || 1b21:0612 || 5.10.0-19-arm64 (Debian) || style="background:PaleGreen;" | good || Using with 2 SSDs in a software RAID-1 array (~190MB/sec for reading and writing)
|-
| SATA Controller || QNINE 4-Port, Marvell 88SE9215 chip || || Ayufan-5.6.0-1137 || style="background:LightYellow;" | very slow || Tested with 3 disks in RAID 5. Top speeds were around 50 MiB/s but quickly dropped to below 2 MiB/s due to SATA CRC errors
|-
| SATA Controller || DELOCK 90498, JMicron Technology Corp. JMB58x AHCI SATA controller || 197b:0585 || 5.18.0-0.bpo.1-arm64 (Debian bullseye + backports) || style="background:LightYellow;" | good, but…
|| Tested with 3 disks, two in RAID1, one standalone.
u-boot-rockchip_2023.07 cannot initialize the controller to boot off it.

|| [[User:Lrissman|Lrissman?]]

[[User:ChriChri|ChriChri(u-boot)]]
|-
| Host Bus Adapter || LSI SAS 9211-4i SAS2008 chip, 4-Port SAS/SATA, PCI 2.0, 8 lanes || 1000:0070 || Ayufan-4.4.197 || style="background:PaleGreen;" | good || tested with four disks attached
|-
| Host Bus Adapter || Fujitsu SAS MEGARAID LSI 2008B2 SAS2008 chip, 8-Port SAS/SATA, PCI 2.0, 8 lanes || TODO || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:PaleGreen;" | TODO || needs special MicroSAS cables. Must be flashed to HBA mode? ordered, not yet received || [[User:JPT|JPT]]
|-
| USB Controller || ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller || 1b21:1242 || Mainline-5.15.0-rc5 || style="background:PaleGreen;" | good ||
|-
| DTMB Quad Tuner || TBS Technologies || TSS6514 || Mainline-5.10.21 || style="background:PaleGreen;" | good || TV -> LAN streaming server, 7W idle, 8-10W with one FHD channel streaming
|-
| DVB-T2/C Quad Tuner || TBS Technologies || TBS6205 || 5.10.0-16-arm64 (Debian) || style="background:PaleGreen;" | good || Working well with Tvheadend
|-
| DVB-S2 Dual Tuner || Digital Devices || Octopus CI S2 Pro || 6.1.42-rockchip64 (armbian) || style="background:PaleGreen;" | good || All features are working flawlessly with the latest drivers from Digital Devices
|}

=== NVMe SSD drives ===

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Kernel || Result || Notes || Power options Active only || Save power setting?
|-
| NVMe || Samsung 970 Evo || 500 GB || || Mainline 5.6 || style="background:PaleGreen;" | good || - || defaults || defaults
|-
| NVMe || Samsung 960 Evo || 500 GB || 144d:a804 || Mainline 5.13-rc4 || style="background:#F99;" | doesn't work || Likely due to 64/32 BAR mismatch issue on Linux 5.11+ || defaults || defaults
|}

=== USB hardware ===

{| class="wikitable sortable"

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes || Tester
|-
||Zigbee Bridge || Conbee II || 1cf1:0030 || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:PaleGreen;" | good || seems to work fine || [[User:JPT|JPT]] ([[User talk:JPT|talk]])
|}

=== USB C alternate mode DP ===

Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

=== eMMC / SD drives ===

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Read Speed || Write Speed ||Result || Notes
|-
|}

=== Other hardware ===

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

== Limitations ==

=== Older firmware overwrites actively used memory ===

Some people get system freeze when:

* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

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

Both issues are in fact the same software BUG. There is no hardware problem. Currently, most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.

People are currently fixing this BUG, but it may take some time. In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip.

Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

Prerequisite packages (Debian/Ubuntu): <code>device-tree-compiler python gcc-arm-non-eabi flex bison gcc-aarch64-linux-gnu gcc make</code>

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

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

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

=== PCIe Controller Hardware Error Handling Bug ===

There is an issue with the rk3399 pcie controller that is currently unmitigated:

* [https://lore.kernel.org/linux-pci/CAMdYzYoTwjKz4EN8PtD5pZfu3+SX+68JL+dfvmCrSnLL=K6Few@mail.gmail.com/ LKML Original Thread]
* [https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

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

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

=== Virtualization ===

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

[[Category:ROCKPro64]]

ROCKPro64 Hardware compatibility

2023-09-25T07:08:45Z

ChriChri: /* PCIe devices */

Hardware accessory compatibility for the [[ROCKPro64]]. Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

== Hardware compatibility ==
=== PCIe devices ===
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes || Tester
|-
| NIC || Intel I350 Dual Port || || Mainline-5.4 || style="background:PaleGreen;" | good || SR-IOV fails
|-
| NIC || Intel I350 Quad Port || || || ? ||
|-
| NIC || Intel X520 Dual Port || 8086:10fb || Mainline-5.6 || style="background:PaleGreen;" | good || SR-IOV fails
|-
| NIC || Intel X550-T2 Dual Port || 8086:1563 || 5.15.0-trunk-arm64 (Debian) || style="background:PaleGreen;" | good || netperf throughput in FW mode, 20 streams: between 4136-6613mb/s across use cases.
|-
| NIC || Intel 82571EB Dual Port (HP NC360T) || || Mainline-5.6 || style="background:#F99;" | crash || kernel crash on boot
|-
| NIC || Intel 82575EB Dual Port (AOC-SG-I2) || || Mainline-5.10 || style="background:#F99;" | crash || kernel crash on boot
|-
| NIC || Intel 82575/82576 || 8086:1521 || OpenWrt 21.02-rc1 ; 5.4.111-1 || style="background:PaleGreen;" | good ||opkg: kmod-igb ; [https://wiki.pine64.org/wiki/ROCKPro64_Software_Release#OpenWrt_21.02 OpenWrt 21.02-rc1] 5.4.111-1 ; ~92.8 KB ; Kernel modules for Intel(R) 82575/82576 PCI-Express Gigabit Ethernet adapters.
|-
| NIC || Aquantia 10GBps AQC107 || 1d6a:07b1 || Mainline 5.16 || style="background:PaleGreen;" | good || Works perfectly out of the box.
|-
| GPU || nVidia GTX-645 || || Mainline-5.4 || style="background:#F99;" | crash || BAR size too small, triggers PCIe error handling bug
|-
| PCIe Switch || PCIE-EUX1-04 Ver.002 || || Mainline-5.4 || style="background:PaleGreen;" | good ||
|-
| SATA Controller || ASM1062 4-Port || || Mainline-5.6 || style="background:PaleGreen;" | good || tested only with one disk attached
|-hw
| SATA Controller || ASM1062 (rev 02) 4-Port ||1d87:0100|| Ayufan-4.4.190 || style="background:PaleGreen;" | good || tested with four disks, 3 in raid 5
|-
| SATA Controller || IOCrest (Same as Syba?) SI-PEX40063 4-port, Marvell 88SE9235 chip || 1b4b:9235 || Debian unstable 5.7, 5.8 || style="background:PaleGreen;" | good || Tested with two disks. SATA errors occurred with a WD Red drive in a cheap enclosure; resolved by connecting the same drive directly to the card.
|-
| SATA Controller || Ziyituod SATA Card ASM 1062+1093 6-Port || 1b21:0625 || Mainline-4.4 (armbian) || style="background:PaleGreen;" | good || tested with 6 disks ||
|-
| SATA Controller || BEYMEI RAID 4-Port, Marvell 88SE9230 chip || 1b4b:9230 || Ayufan-5.6.0-1137 || style="background:PaleGreen;" | good || Tested with 3 disks in RAID 5. I added pci=nomsi to /boot/extlinux/extlinux.conf kernel parameters and an udev rule before the disks were recognized: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x1b4b", ATTR{device}=="0x9230", RUN+="/bin/bash -c 'echo %k > /sys/bus/pci/drivers/ahci/bind'"
|-
| SATA Controller || BEYIMEI SATA Card 6-Port, ASM1166 chip || || 5.10.0-16-arm64 (Debian) || style="background:PaleGreen;" | good || Tested with 4 disks. Built 2 separate software RAID-1 arrays without errors. Performance seems good enough for a NAS on gigabit LAN.
|-
| SATA Controller || PCE8SAT-A02 VER006S 2 Lanes, 8-Port, ASM1166 chip Odd because chip got only 6 ports?|| 1b21:1166 || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:#F99;" | unstable || Tested with 3 disks in SW-RAID 5. After 10 hours of burn in test one disk dropped from system *and* RAID. Hotplug does not work. || [[User:JPT|JPT]]
|-
| SATA Controller || BEYIMEI SATA Card 2-Port, ASM1062 chip || 1b21:0612 || 5.10.0-19-arm64 (Debian) || style="background:PaleGreen;" | good || Using with 2 SSDs in a software RAID-1 array (~190MB/sec for reading and writing)
|-
| SATA Controller || QNINE 4-Port, Marvell 88SE9215 chip || || Ayufan-5.6.0-1137 || style="background:LightYellow;" | very slow || Tested with 3 disks in RAID 5. Top speeds were around 50 MiB/s but quickly dropped to below 2 MiB/s due to SATA CRC errors
|-
| SATA Controller || DELOCK 90498, JMicron Technology Corp. JMB58x AHCI SATA controller || 197b:0585 || 5.18.0-0.bpo.1-arm64 (Debian bullseye + backports) || style="background:LightYellow;" | good, but…

|| Tested with 3 disks, two in RAID1, one standalone
u-boot-rockchip_2023.07 cannot initialize the controller to boot off it
|-
| Host Bus Adapter || LSI SAS 9211-4i SAS2008 chip, 4-Port SAS/SATA, PCI 2.0, 8 lanes || 1000:0070 || Ayufan-4.4.197 || style="background:PaleGreen;" | good || tested with four disks attached
|-
| Host Bus Adapter || Fujitsu SAS MEGARAID LSI 2008B2 SAS2008 chip, 8-Port SAS/SATA, PCI 2.0, 8 lanes || TODO || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:PaleGreen;" | TODO || needs special MicroSAS cables. Must be flashed to HBA mode? ordered, not yet received || [[User:JPT|JPT]]
|-
| USB Controller || ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller || 1b21:1242 || Mainline-5.15.0-rc5 || style="background:PaleGreen;" | good ||
|-
| DTMB Quad Tuner || TBS Technologies || TSS6514 || Mainline-5.10.21 || style="background:PaleGreen;" | good || TV -> LAN streaming server, 7W idle, 8-10W with one FHD channel streaming
|-
| DVB-T2/C Quad Tuner || TBS Technologies || TBS6205 || 5.10.0-16-arm64 (Debian) || style="background:PaleGreen;" | good || Working well with Tvheadend
|-
| DVB-S2 Dual Tuner || Digital Devices || Octopus CI S2 Pro || 6.1.42-rockchip64 (armbian) || style="background:PaleGreen;" | good || All features are working flawlessly with the latest drivers from Digital Devices
|}

=== NVMe SSD drives ===

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Kernel || Result || Notes || Power options Active only || Save power setting?
|-
| NVMe || Samsung 970 Evo || 500 GB || || Mainline 5.6 || style="background:PaleGreen;" | good || - || defaults || defaults
|-
| NVMe || Samsung 960 Evo || 500 GB || 144d:a804 || Mainline 5.13-rc4 || style="background:#F99;" | doesn't work || Likely due to 64/32 BAR mismatch issue on Linux 5.11+ || defaults || defaults
|}

=== USB hardware ===

{| class="wikitable sortable"

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes || Tester
|-
||Zigbee Bridge || Conbee II || 1cf1:0030 || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:PaleGreen;" | good || seems to work fine || [[User:JPT|JPT]] ([[User talk:JPT|talk]])
|}

=== USB C alternate mode DP ===

Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

=== eMMC / SD drives ===

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Read Speed || Write Speed ||Result || Notes
|-
|}

=== Other hardware ===

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

== Limitations ==

=== Older firmware overwrites actively used memory ===

Some people get system freeze when:

* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

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

Both issues are in fact the same software BUG. There is no hardware problem. Currently, most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.

People are currently fixing this BUG, but it may take some time. In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip.

Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

Prerequisite packages (Debian/Ubuntu): <code>device-tree-compiler python gcc-arm-non-eabi flex bison gcc-aarch64-linux-gnu gcc make</code>

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

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

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

=== PCIe Controller Hardware Error Handling Bug ===

There is an issue with the rk3399 pcie controller that is currently unmitigated:

* [https://lore.kernel.org/linux-pci/CAMdYzYoTwjKz4EN8PtD5pZfu3+SX+68JL+dfvmCrSnLL=K6Few@mail.gmail.com/ LKML Original Thread]
* [https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

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

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

=== Virtualization ===

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

[[Category:ROCKPro64]]

ROCKPro64 Getting Started

2023-09-25T07:04:23Z

ChriChri: /* Booting from SATA - alternative way to setup */

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

== Video Playback ==

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

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

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

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

== Using an NVMe Disk as rootfs ==

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

== Setup a Serial Console (UART2) ==

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

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

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

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

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

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

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

$ screen /dev/ttyUSB0 1500000

$ picocom /dev/ttyUSB0 -b 1500000

$ minicom -D /dev/ttyUSB0 -b 1500000

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

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

GNU/Linux:

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

== Booting from USB or PXE ==

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

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

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

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

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

=== Alternative way to setup ===

There's a howto about creating software raids on sata disks for your system, installing u-boot into SPI to boot of the software raid and configuring boot using an Armbian Installation on eMMC/sdcard. All of the work can be done from the linux command line or even remote via ssh.

https://git.sr.ht/~chrichri/RockPro64_u-boot_SATA_software_RAID_howto

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

== Booting from SPI using u-boot ==

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

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

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

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

== Boot sequence ==

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

== OTG Mode ==

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

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

== NVMe Drives ==

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

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

== SATA Drives ==

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

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

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

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

== 7" LCD Touch Screen ==

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

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

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

== RTC Battery Backup ==

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

== Acrylic Open Enclosure ==

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

== NAS case ==

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

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