Hi. 

There is a "DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P" listed within the SOPINE Extension ports. 

I'd like to attach the camera with 2 lanes MIPI (D0, D1, C pairs), I2C and two GPIOs. 

Is there a support in firmware for such camera? Or at least firmware easy to adopt? 

Thank you! 

Hello,

I am just relaying that NetBSD is now available for the Rock64. You can download their images from: http://www.invisible.ca/arm/
Many thanks to Jared McNeill

I had no audio/sound with bionic-lxde images, I tried pre-release 0.6.55 so went to release 0.6.44 but had same problem. I tried google but not find answer, so google more to learn about ALSA and pulseaudio, seems problem with pulseaudio default sink, and I created following file and now can get audio.
If you get no audio, give this a try.

rock64@rock64:~$ cat ~/.config/pulse/default.pa
.include /etc/pulse/default.pa
set-default-sink alsa_output.platform-hdmi-sound.stereo-fallback

rock64@rock64:~$

I'm using ayufan's latest image with the ROCK64 connected to a 4K display and the display says the input is 4K resolution. 
image: android-7.1-rock-64-rock64_atv-v0.3.4-r86-raw_sd2emmc.img.xz

However if you issue the command 
     "adb shell dumpsys SurfaceFlinger"

The framebuffer is 1920x1080.  When playing a 4K video using VLC (or any other player) you will see the video is 4K, but is scaled to the framebuffer 1920x1080 and then the HDMI display logic would scale it back to 3840x2160.   When issuing the same commands on a NVIDIA shield the framebuffer is 3840x2160, so no down and up scaling occurs. 

Admittedly behind the scenes the scaling might not be happening.  Does anyone know if this is the case?

Steve

Hi everyone,

I used the latest stable image of OpenMediaVault (microSD Boot) which at the current time of posting is stretch-openmediavault-rock64-0.6.44-239-armhf.img.xz as recommended by the release notes. I wrote the image to a Samsung Evo 32gb microSD card using latest version of Etcher and put it on my recently bought Rock64 4G. It boots up properly and I can access the web GUI. The problem is that the system date and time are not correct. I've spent several hours trying to get it to set the date and time correctly through NTP but no luck.

When booting for the first time and accessing by SSH, when I ran any of the following commands, It gives me an incorrect date and time (May 27th 2017, time is not even close to real current time).

Added Armbian Debian Stretch Desktop (ROCK64) 5.42 on Wiki and PINE64 Installer.
Added Armbian Ubuntu Xenial  (ROCK64) 5.42 on Wiki and PINE64 Installer.

Hello all, 

I am admittedly a novice when it comes to the rock64. I recently purchased one through the pine64 store along with the recommended power supply.

I am attempting to use it as a little NAS running the stretch-openmediavault-rock64-0.6.44-239-armhf.img.xz. I loaded the image via etcher onto a 32gb sandisk sd card and when I power up the device I get white, red and green lights all solid and unchanging. Ethernet lights never light up (plugged into router lan part via verified working cat5 cable) and no output is displayed via the hdmi port.

I have tried 2 or 3 versions of the stretch openmediavault, the most recent being 0.6.57-270 and the results have not changed.
I tried Armbian Xenial Legacy Kernal 4.4.y flashed with win32diskimager and the result was the same... white, red and green lights, no ethernet, no hdmi output.

I'm not sure where to go from this point and any help would be greatly appreciated.

had to remove this package to get it working

apt-get remove golang-docker-credential-helpers

I just got my ROCKPro64 (from the first batch) a week ago in the mail, and some capacitors have obviously shifted during production, and some soldering bridges are also present. Has anyone else had such issues?

I tried to take some photos with the microscope at our university lab, this didn't turn out too well, hopefully you can still see what I mean... Also, support wasn't really helpful in this issue

Hi

After  installing a Linux downloader  I have managed to download many Linux distro's from Github.

My board is a pre production Rockpro64_V2 2018-4-11

Trying with many Linux images and Android, also 3 different 12v power supplies I constantly see a major issue to achieving  successful booting.

Symptoms.

Board set up with SD card or emmc media loaded with bootable image, (any). Serial console connected.

1. insert 12v power jack... System starts to boot, either gets errors loading  and crashes or succeeds with NO errors about 50% of power ups.  Sometimes errors are shown on console,  initialising USB3 interface for example, and errors from  image CRC on media.

2.  With successful booted system, (logged in),   pressing reset reboots system, then reboot starts to occur,   ALWAYS (100%) fails to conclude boot, most often hangs at end of Uboot load.

3.  Pressing power switch either does nothing, no reboot  or reboots to hang at end of Uboot as above.

4. Pulling 12v power jack out and reinserting successfully reboots to login prompt. 100%  (after successful boot from initial power up (1. above)

This is repeatable!

The first thing that strikes me is that the board starts to boot at the INSTANT of power connection.  There does not appear to be any delays to allow power supplies to settle,  there needs to be a short delay to allow the power supplies on the board to stabilise before the boot runs.

It seems as though the  SBC logic is not cleared or reset properly on initial power up.  in fact the reset does nOt reset properly.

It appears that the reset push button doesn't reset properly.

It appears that once the system has booted correctly then it is more likely to boot correctly on subsequent reboots (by pulling and reinserting 12v jack).

I cannot find the post at the mo, but someone else was complaining about random boot errors.

I am wondering whether the board is electrically "noisy" and is suffering from an inadequate ground plane, or perhaps lack of filtering on the logic  supplies.   How many layers are there in the pcb? I am certain this is an electrical problem and not software.

I hope this issue has been addressed in the second batch of boards to be released.  This board is very flakey at the moment.  It still needs a lot of work!

regards

Patrick