Hi,

When the next batch of RockPro64's comes in I'll be ordering, but just had a quick question on ordering the ROCKPro64 12V 5A EU Power Supply, for people in the UK will this come with the a UK power plug lead or will I have to source this separatly ?

The ROCKPro64 first stock Android 7.1.2 build released, and please download at PINE64 wiki site:
http://wiki.pine64.org/index.php/ROCKPro...e_Releases

- This build support PINE64 7" LCD panel
- This is typical Android UI, not Android TV type
- This build doesn't have Google Play app and will include on next build

Hi all, I'm looking for help with tftp boot from SPI flash.
Booting from flash works fine, the rock boards load their pxelinux.0 from tftp. Then for some reason the bootloader seems to ignore my 'fdt /dtb' entry and requests /dtb/rockchip/rk3328-rock64.dtb.

After successfully loading this file it throws the following error:

Filename 'dtb/rockchip/rk3328-rock64.dtb'.
Load address: 0x1f00000
Loading: ####
         1.8 MiB/s
done
Bytes transferred = 56922 (de5a hex)
## Starting EFI application at 02000000 ...
efi_load_pe: Invalid DOS Signature
## Application terminated, r = 9223372036854775806

Can someone provide any insight on why this happens and how to fix it?

Thanks!

For the sake of completeness here's my pxelinux.0:
default rock64-kernel-4.4
prompt 0
timeout 3

menu title Boot options

label rock64-kernel-4.4
   kernel /Image
   initrd /initrd.img
   fdt /dtb
   append earlycon=uart8250,mmio32,0xff130000 rw root=/dev/nfs nfsroot=${serverip}:/data/rootfs/rock64-1 rootwait init=/sbin/init mtdparts=spi32766.0:32k(system),4064k(loader),3840k(reserved),256k(vendor),4M(uboot),4M(atf)

I ran into a problem with my Rock64 recovering from a power outage recently, and had to unravel it from its installation, plug it into a TV and reboot it there to diagnose.

The RPis have things like these screens available, often with a nice case to go with.

Does anyone have any experience with those or others? The drivers for those seem to be pre-built binaries specifically for the Rpi, so I doubt it would work.

Thanks,
R

Hi, can i have the source code of the android image that its on the wiki?

Hi All,

I am coaching two undergrads through a summer research experience doing a deep dive into Linux kernel hacking.

I expect we're going to break the kernel a whole lot. My first task is to master recovering from this gracefully.

Leveraging dim memory from the last time I did something like this (a VAX 11/780 with Berkeley Unix), multiple kernel images could reside on disk (including a known good image). The boot loader could be instructed which to load.

I suspect the process on the Rock64 is similar... Would you be willing to comment if I'm on the right track:

- add USB UART to board.
- ensure U-Boot is flashed
- boot into U-Boot ... select kernel image... boot

Does the FLASH come with U-Boot already present? 

Thank you a lot - I am happy to answer any questions you might have about our project (introduce a multiple personality disorder into Ubuntu).

The first image I loaded on my R18 LTS board was Ubuntu 16.04.3 LTS. It loads fine, but the login credentials say to use ubuntu for the username, and ubuntu again for the password.  Bu that does not work.

I tried rebooting the board several times, and I'm not a Newbie either. I expect that nobody is going to know why the passwords don't work, because support never re[plied when I asked them. 



The first two lines that come to the screen are numbers with the words Trace.Call after them. What is that about, is the image notifying someone that I am using it?  I'm not new to Linux, so that had to be added by whoever created the image.

In any case, has anyone any ideas about the Passwords for ubuntu not working?

Joe

Hello,

I've build my own RFLink using an arduino. It work very well on RPi.

But I have problem to make it work on Rock64. It worked this morning but after a restart (sudo reboot), it didn't work anymore.
Domoticz is configured to connect to RFLink via /dev/ttyUSB0.
After the restart, I have this error :

Quote:Error: RFLink: Error opening serial port!

Hi all,

I have a problem with the usb3 ports. I run an arch linux installation on a rock64. I followed the instructions in this thread 
https://forum.pine64.org/showthread.php?tid=5001
and that helped me to get usb2 ports working. But I can't do the same thing for the usb3 ports (toggle the right gpio to switch the regulator for usb3 on). Mostly I don't know, which gpio port belongs to the usb3 regulator.

Maybe someone can give me a hint.

Thanks in advance and

Best regards,
Christoph