Hello.

I am here to ask for the community to help. In the past week some users have taken it upon themselves to contribute to RockPro64 section of the wiki and have done a much greater job that I could have hoped for. I am linking this section as I will refer back to it in this post since it has the preferred standard, content and structure.

But the RockPro64 is just one section out of 9 (not counting subsections) sections; it would be great to see more engagement in the remaining parts - especially from the regulars on the forum - who would ideally help in editing, contributing to, and maintaining the wiki. That said, every forum member with privileges to post un-moderated content on the forum is also allowed to edit the wiki.

To be more precise here is what needs to be done / what I'd like help with:

1. Update and improve the project section. Instructions regarding structure and contents of the section can be found at the top of the section. Help in this section would include: i) adding the RockPro64 and Pine H64 to the matrix ii) finding and adding projects that user have created in the past 6 months iii) helping maintain the section.
   
2. Update the i) Rock64; ii) Pine A64; iii) Pine A64-LTS / SOPine; iv) Pine H64; and v) Pinebook sections. For inspiration and structure please look at what community has done with the on the aforementioned RockPro64 subsection of the wiki. I am aware that this is a significant task - each and single one of the main board sections would require a number of hours. If you're up for it, make sure to let me (and others) know so that workload can be divided up.
   
3. Keep the build versions and links up-to-date - this goes for all PINE64 devices.
   
4. Add new Linux, *BSD and Android builds for the respective devices. In short, if you see that a OS image has been pushed or a new one was made available then please update the wiki with it in the relevant section. New builds pop up everyday and developers don't always make us aware of their work. Sometimes we also miss their messages (this is just one recent example). Its impossible to follow all third-party development and always stay on-top of adding builds - help with this would be much appreciated.
   
5. Update the NOOB section with information relevant to the PineH64 and RockPro64. This would include editing the wiki for instances where e.g. instructions for flashing list particular boards (currently neither are listed anywhere) or where board specific instructions are provided.
   
6. Come up with a comprehensive idea for this section, develop it and help maintain it. 
   

I have got a RockPro64 straight form the factory mid /endJul second batch. It wont boot any of the images.
after burn I have 7 partition (5 unknown loader 1 & 2 etc)



Error


I have tested  2 diff sd pro cards, latest from wiki bionic, stretch no go.

Im booting from SD. Jumper J15 open should work since only SD card inserted to boot.
User etcher and w32.

What do you think?
Is it the board or something else wrong

Greetings everybody,

Today on my quest to enable the rock64 for my purposes I had just one goal:
Install upstream debian testing (buster) without any customizations.

Sadly I did not achieve this goal fully; However I believe I got extremely close. See below for the one bugreport I opened to have the last piece upstreamed.

So here are the steps from an existing debian system running on the board (mostly in pseudo-code because the difficulty level isn't novice):

0. Install U-Boot to SPI Flash
- https://github.com/ayufan-rock64/linux-u-boot/releases

1. Partition (e)MMC
 - 100MiB EFI partition (fat)
 - 1GiB boot partition (ext4)
 - 57GiB rootfs partition (f2fs)

2. mount filesystems
 - rootfs: /mnt
 - boot: /mnt/boot
 - efi: /mnt/boot/efi

3. bootstrap debian
 - debootstrap --arch=arm64 --variant=minbase buster /mnt http://deb/debian.org/debian

4. mount additional filesystems
 - mount -vt sysfs sysfs /mnt/sys
 - mount -vt proc proc /mnt/proc
 - mount --bind /dev /mnt/dev
 - mount --bind /dev/pts /mnt/dev/pts
 - mount --make-rslave /mnt/dev
 - mount --make-rslave /mnt/dev/pts

5. install additional software
- tasksel ssh-server (this is a little messy in a chroot)
- apt install linux-image-arm64 grub-efi-arm64
- apt install ifupdown locales

6. configure system
 - /etc/initramfs-tools/modules: f2fs
 - /etc/default/grub: GRUB_CMDLINE_LINUX="earlycon=uart8250,mmio32,0xff130000 console=ttyS2,1500000"
 - /etc/default/grub: if [ -z "$GRUB_DEVICE_UUID" ] && [ -n "$GRUB_DEVICE" ]; then GRUB_DEVICE_UUID=`blkid -s UUID -o value "$GRUB_DEVICE"`; fi
 - dpkg-reconfigure locales
 - dpkg-reconfigure tzdata
 - /etc/network/interfaces: auto eth0
 - /etc/network/interfaces: iface eth0 inet dhcp
 - /etc/network/interfaces: iface eth0 inet6 auto

7. make it bootable
 - update-initramfs -u
 - grub-install --target=arm64-efi --removable
 - update-grub
 - copy /usr/lib/linux-image-4.17.0-1-arm64/rockchip/rk3328-rock64.dtb to /boot/efi/rockchip/rk3328-rock64.dtb

At this point the system could be rebooted and should automagically start up through grub.However one piece is still missing:
When the DTB gets updated with a new debian kernel, the copy on the EFI partition has to be updated as well.
For this we use the debian specific flash-kernel application by adding the following entry to /etc/flash-kernel/db:

Any one had success running LibreELEC? In the wikipage has a link for LibreELEC images but a couple of days ago only a .tar file was available at the pointed repository, not a flashable img.gz.

Today, i checked the repo and an .img.gz file had appeared. Just flashed a MMC, but the system wouldn't boot.
Maybe SD? Any one had success with it?

PS: I find it very misleading the official wikipage point to an image that won't even boot. I suggest to remove the link, there.

RK3399K (2GHz/1.6GHz) for next revision ?

One of the main reasons I bought a rock64 was the promise of being able to play 4K videos yet I have so far not managed to go much longer than 5m of 4K video playback before kodi freezes or reboots my rock64. Before I attached a heatsink to its CPU it would struggle to last even 1m when playing 4K videos under kodi so now I presume it is my PSU at fault because no-one else seems to be having such issues with kodi.

I am currently using an atolla 5V/3000mA PSU (model BYX-0503000B) that I bought off Amazon. It seems to work OK but I don't have a multimeter or anything to check that it is actually supplying the claimed output. I would prefer not to order a PSU from pine because it costs a lot to have things posted from the US to the UK and also it seems that the PSU they sell is a US PSU that requires an adapter to plug into a UK mains socket. I would rather get a PSU with a UK plug that doesn't require an adapter, ideally.

If there are any UK rock64 users reading this that have a working 'native' PSU and can confirm you can use kodi to watch 4K videos for more than 10m (ideally I'd be able to watch feature length 4K films without any reboots or freezes) then please tell me the make and model of your PSU and where you bought it from.

Thanks!

I was on Debian Stretch, but the WiFi went wrong so Im trying different OS's, Im now on Armbian because it seems to have good tools for wifi like nmtui.

I have the official USB wifi from the Pine website, its the Realtek one.

I flashed Ambian Ubuntu Xenial using the PINE64 flash tool.

I started it set the passwords. 

iwconfig shows the wlx0013ef800c2c and p2p0 as wifi devices.

I try nmtui-connect <my ssid> enter the PSK and it fails to connect.

I go to nmtui and multiple wifi networks are available, select mine, enter the PSK and it still fails to connect.  I set the PSK to viewable and confirm it is correct, still no luck.

I try iwconfig wlx0013ef800c2c essid <my ssid> key <my psk>, this gives no output, but on checking the ifconfig, no connection has been made.

Please can anyone help me to troubleshoot this.

THanks both of you who answered my last post.

I am a visual type person and found a video of someone installing OMV and booting it on Rock64
It pertains to this video   https://youtu.be/gT-EGNl9bZA   ROCK64 OpenMediaVault NAS  at 7:35 in the video.

Question, while booting he looks and gets the IP address as he will need it for the OMV program later. Just below the IP Address there is a PROMPT FOR ROCK64 LOGIN:

next part of video, it shows OMV booted.  ((DO YOU HAVE TO LOGIN THERE OR HIT ENTER FOR IT TO FINISH BOOTING?
IF I DO HAVE TO LOG IN, WHAT IS THE PRESET "ID" AND "PASSWORD" AT THAT POINT?

Watch all up to that point.  you will see what I mean.  I am sure you have worked with OMV before and can answer if I have to login at that point. and with what password/if a default one.


OH,  Is there any issue with ROCKPRO64 identifying the ROCKPro64 PCI-E to Dual SATA-II Interface Card?

Or does that issue pertain to the M2 storage card slot?

I decided to buy 2 qty ROCKPRO64s  WITH THE DUAL sata-II Interface Card for each.

set one as NAS  and other as a workstation.

Hi,

I received a couple of months ago two ROCK64 4GBs as well as two 64GB eMMC modules. Yesterday, I finally began trying to get them up and running. I'm planning to run my home automation and NAS on them, so I'd be getting Armbian Stretch on them. I failed to order the eMMC USB adapters (mistake!), so getting the eMMCs flashed were a bit problematic. I finally did the following:

I installed these prerequisites:

https://github.com/ayufan-rock64/flash-tools

https://github.com/ayufan-rock64/rkdeveloptool

Next, I got myself a USB A-A cable (actually had an USB B-B adapter which worked well with a couple of USB A-B cables - the other alternative would've been to splice two USB cables).

Then, went through the following process:

1. Placed a jumper on the maskrom headers (the ones closest to the Recovery button)
   
2. Connected the USB cable to the upper (OTG) USB port
   
3. Connected the power cable
   
4. After a few seconds, removed the jumper
   

Hi guys,

I want to make myself a 4K video player with Rock64. I've got a 2GB version of it. I've tried some combinations of OS images and players. So far, my Rock64 can't play 4K video smoothly. No problem with 1080p videos. The list of OS and players combinations I tested is as below:

android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img + kodi-17.6-Krypton-arm64-v8a.apk

android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img + MX Player 1.10.2.1 beta.apk

android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img + VLC Player (default player in the image)

LibreELEC-RK3328.arm-9.0-devel-201807011300-d46baa3-rock64.img + Embeded Kodi

LibreELEC-RK3328.arm-9.0-nightly-20180816-eef941c-rock64.img + Embeded Kodi

LibreELEC-ROCK64.aarch64-8.2-devel-20171004193222-r26173-gd404dbb.img + Embeded Kodi

Armbian_5.42_Rock64_Debian_stretch_default_4.4.124_desktop + Embeded MPV

Could anybody please tell me how to configure my rock64 for smooth 4K video playing?

P.S. the 4K video I tested is encoded with H.265.

Thanks a lot!