Hi all,

I'm using a RockPro64 board with a eMMC.

I succesfully flashed an Armbian image to this emmc, and I can boot it without problems.

I tried to disable boot from SPI (placing a jumper on pins 25-23 on PI-2 connector) and I'm able to boot from eMMC (u-boot spl and u-boot are loaded from there).

I tried to compile a u-boot.itb from scratch using Ayufan's repo https://github.com/ayufan-rock64/linux-u-boot/ and I flashed it to eMMC using USB OTG cable and rkdeveloptool at offset 0x4000. But old bootloader stills boot, as my bootloader were flashed not in the right place.
Besides that, I can use rkdeveloptool only if I stop u-boot and then run command

rockusb 0 mmc 0

Additionally, only first of two scenarios reported here https://wiki.pine64.org/index.php/ROCKPr...e#OTG_mode is working, because if I disable SPI and eMMC with jumpers (so no bootloaders present) my board enter in MaskMode but rkdeveloptool does not work (seems unable to communicate with board).

What I'm doing wrong?

Thanks in advance, regards

mauro

Hi.

I'm trying to get hyperion(https://github.com/hyperion-project) working, but can't seem to be able to get any of the grabbers working in LibreElec while it plays videos using hardware decoding.

As far as i know, LibreElec doesn't use the framebuffer while playing videos, as it doesn't work if you want hardware decoding. Instead, i think it uses the Rockchip MPP module to communicate with the hardware directly.

Does anyone know of any way i can grab a screenshot of what is currently being either outputted to HDMI or currently being decoded etc.?

The Raspberry pi can apparently do this through its dispmanx API. can we do something similair on the rockpro64?

I wrote up a small tutorial on installing openbsd on the pinea64-lts model:
https://github.com/epsilon-0/openbsd-pine-a64-lts

Hope it helps some people

Added AOSC Community Build Image with Mate Desktop (microSD Boot) - 20190218 to Pine64 Installer
Added AOSC Community Build Image with Mate Desktop (eMMC Boot) - 20180216 to Pine64 Installer

Hi,
I received my new Pinebook yesterday, newest model with 1920 x 1080 screen, all is awesome with the exception I am not able to get the HDMI output to work.  I have used 2 different monitors and get the same result, both show that a signal is present and switch to that input however neither will display any video or audio.  I have used the same cable with both monitors with my dlsr cameras as well as other devices and all works with other devices.  I am using KDE Neon as was preinstalled with all current updates and everything else is perfectly working otherwise.  Am I missing something?

Thank you

Today I received my Pinebook. Here are my first impressions, not ranked by seriousness or whatever, just how I remember them:

- DHL charged almost 15 euro ON TOP of the import taxes, as a fee for lending me the import tax for a day or two. If a bank would charge this as interest, it would be illegal. As fraction of the purchace price, 15% is rather much. Please use another shipper next time.

- The keyboard feels very nice! The size and weight are great. I have a macbook from work, and its screen is hardly larger, and I like the pine keyboard feel better.

- However, there is no key with ' and " on it, which is usually left of the Enter key. That is a very important key for programming... Using the Fn+-_ key is not really a good substitute.

- The key labeled \ and | does not produce these characters (in US keyboard layout), but < and > . That is also annying.

- Lots of graphics glitches. Menus, or letters in Konsole, have random horizontal lines in them. Graphics are also very slow. Several of the desktop effects such as a cube when switching workspaces do not work.

- My pinebook hang a few times while doing something graphical.

- The video players seem to use the wrong stride for the display. The image is unwatchable but it seems every next lower line is offset many pixels to the right. At first I thought it might have been because I had set a screen magnification factor as recommended, but when I undid this, the effect remained.

- The clickpad is weird, in the sense that it clicks only near the bottom corners. I have not found a way to click the middle button, which is very important for X pasting.

Hopefully I will f]find out somewhere in the forum what to do about these things :-) I typed this on the Pinebook :)

I've just received my Rock64 and discovered that unfortunately a lot of the ports (plus some extra things) are misaligned and/or damaged. Not severe enough to interfere with its operation (I hope), but as I'm hoping to put this in a Pi case I may struggle a bit with them like this.

The cardboard box it came in doesn't have any signs of damage, and no pins appear to be bent or broken, so this doesn't seem like shipping damage but rather poor quality assembly.

What is the best course of action right now? I'm able to re-solder most of these parts myself but would rather not do that to a brand new board unless absolutely necessary...

The affected parts are:
Power jack (bent up and sideways), IR sensor (leaning sideways), USB3 port (leaning down/forwards), USB2 ports (damaged on the bottom), Ethernet (bent top which may be normal, slightly melted on the bottom), Power button (rotated), GPIO headers (inconsistent solder, possibly dry joints).

Photos:

hello, please help me connect 4pcs ds18b20 and thermometer display

Hello.

I'm running libreelec on my RockPro64. I'm currently controlling it using yatse on my phone but I would like to use my amp IR remote. 
I plugged an IR receiver module on the appropriate socket on the board, I set up kodi to work with my amp remote (using the instructions from librelec wiki) but the remote doesn't work.
It seems that there is no IR driver loaded.

I downloaded the NetBSD Pinebook image from invisible.ca (https://www.invisible.ca/arm/) and created a microSD card, as directed using Etcher. My Pinebook (1080p) booted, but when I dd'd the image to /dev/rdl2c I got a ton of errors. Now my Pinebook does not boot, unless there is a SD card inserted.

arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m conv=sync
    dd: /dev/rld2c: Input/output error
    30+0 records in
    29+0 records out
    30408704 bytes transferred in 11.143 secs (2728951 bytes/sec)
This generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen.

My disklabel looks like this:
arm64# disklabel ld2

    # /dev/rld2:

    type: ld

    disk: ld2

    label: default label

    flags:

    bytes/sector: 512

    sectors/track: 63

    tracks/cylinder: 32

    sectors/cylinder: 2016

    cylinders: 1040

    total sectors: 2097152

    rpm: 3600

    interleave: 1

    trackskew: 0

    cylinderskew: 0

    headswitch: 0           # microseconds

    track-to-track seek: 0  # microseconds

    drivedata: 0

    5 partitions:

    #        size    offset     fstype [fsize bsize cpg/sgs]

     c:   2097152         0     4.2BSD      0     0     0  # (Cyl.      0 -   1040*)

     e:    163840     32768      MSDOS                     # (Cyl.     16*-     97*)

    disklabel: boot block size 0

    disklabel: super block size 0
    disklabel: partitions c and e overlap

Any ideas on how to get NetBSD running on my brand new Pinebook?

[url=http://www.invisible.ca/][/url]