This section gives important information to get the board up and running.
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 video playback here. For your ROCKPro64 the install should be
sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm
(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
Forum member Bullet64 has documented how to move rootfs to an NVMe disk. This is useful until we get a full SPI option to boot from the NVMe.
|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).
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 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
|You might need a root permission if your user is not in the appropriate user-group e.g.
dialup on GNU/Linux
Alternatively there is a detailed guide on forums: https://forum.pine64.org/showthread.php?tid=6387
With GNU/Linux on your RockPro64 the built-in support for serial console can be enabled by parsing parse e.g.
console=ttyS2,1500000n8in the kernel command line, many distributions make this available by default, but consider verifying the contents of
/boot/extlinux/extlinux.confif you encounter issues.
n8in the kernel argument means no parity, 8 bits per character
The default choice of boot device is first eMMC (if present) then SDcard. See ROCKPro64 under "jumpers" 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 useful scripts above).
Background info and historic details of this usage can be found here.
|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
You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see switch 28 under Layout#Switches). Note that 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 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.
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. WD Blue devices.
SATA drives can be connected directly via the ROCKPro64 PCIe interface card. Please note the card does not include the power cable - that is a 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 ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.
If you have bought the Wi-Fi and Bluetooth module from the Pine store then instructions for connecting it can be found on the accessories page. 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.
Instructions for connecting the LCD touch screen from the Pineare on the accessories page.
Note at present (August 2018) this screen is only supported by the Android image.
|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