Hi

I would like to customize DSI settings value (resolution, format, pouch etc.).
Therefore, I am planning to change the setting value from DTS.

Is there any document that describes how to change DTS and how to build it?
If it does not exist, I would like to know how to change DTS and build DTS.

The software and hardware used are as follows.
 software : https://github.com/ayufan-pine64/linux-build (xenial-minimal-pine64-bspkernel-0.7.19-118.img.xz)
 hardware : PINE A64+ 1GB

Thank you.

The StackOverflow community took a look at the schematic for the 20-pin header beside the SOPINE modules on the clusterboard and said that it should be possible to configure the SOPINE hardware to use the UART and SPI pins as GPIO. One user commented:

"Most MCUs and SoCs have multiple functions on each pin. The SPI 'pins' are just one of those alternative functions. As long as you're not using SPI, and don't have it configured, those pins are just plain GPIO pins"

I'd like one of them to operate a simple low-power LED that is either on or off, controlled by software, to indicate busy status (not if the board is powered on or off). Any ideas how to get started?

Hi, 
I would like to ask is it possible to power some HDD from USB 3.0 on Rock64 sbc ? 
I mean without external power - just from usb - probably it should run fine with some external enclosure and 2.5" 5400rpm HDD or SSD ?

Short version:
A functional RockPro64 stopped working, and fails to boot. Clean Reinstall on SD card completed -- no effect, still cannot boot. If plugged in for more than 3-5 minutes the heatsink on the cpu will become noticeably hot to the touch (implying some sort of operation is being run on the cpu). The LED indicator is no longer coming on (i.e. the one that sits directly behind the reset button).

Longer version:
I originally had a RockPro64 that was functional. One day, after using it for a while (I was testing out vnc viewers), I left for a moment and when I returned the device was powered but the screen had shut off. I attempted to wake it (failed), tried to reboot it (failed), unplugged and waited a bit before plugging it back in, it still failed to boot. I then left it for a few minutes and when I came back, the heatsink on the CPU was hot to the touch (yet the LED indicator located behind the reset button which is usually on when the board is on, was off). I unplugged it to let it cool down. Once cool, I plugged it back in and tried to use both the reset button and the power button in an attempt to force the boot sequence to start. Neither produced any results. The board started to get hot again so I unplugged and decided to check the SD card. It seems to be undamaged (all my files were accessible so I was able to retrieve my files). Returned the SD card to the board and tried to boot again -- same result (overheating with a black screen-- no blinking cursor, nothing, I dont think the screen even recognized the input). I decided to bite the bullet and reburn a clean image of the linux distro onto it and try again. No issues during the burn process and I returned the SD card to the board and attempted to boot it). Exact same result -- no lights, no signals, but if you leave it for 5 minutes the heatsink will be hot. The only indication LED that is still on is the DCIN one.

I have tried different computer monitors, to no effect. I think it is also important to note that when the board was functioning normally, the heatsink would remain cool to the touch during the boot up process and even during light usage (i.e. writing some code). Something very abnormal has occured, and I think it is a hardware issue, but I am kind of stuck at this point.

Any insight into what I should attempt next would be appreciated (or confirmation that someone else as experienced something similar).

a kickstarter I backed long ago was the EORA 3D scanner. It took a long time to deliver and after it did I felt that it really needed a full fledged computer to be utilizing it versus a smart phone. It supports Android, however not as well as iOS. I am looking at using the RockPRO64 to make a device that can use the EORA 3D scanner. likely it will also need a robotic arm to hold the camera and scanner. in the past I found that the scanner and cameras needed to be leveled.

I needed to order some parts and saw the cameras were now available so I ordered 2 of those and some other parts. unfortunetly the main system seems to be currently out of stock though so that will have to wait.

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 ?