Hi,

Due to lots of other activities I have not been able to work on Rock64 changes as much as I hoped.
Therefore it has taken far longer than anticipated, but here it is.
I'm pleased to publish a link to the first Volumio dev image for Rock64.
Volumio 2.299 for Rock64

This image will boot from eMMC and uSD out-of-the-box.
Support for the Rock64 DAC board is included, SPDIF and DAC are both working.
Limitations are:
- it is WIP and therefore a dev version, no opportunity to update to a newer release (reflash will be necessary)
- not all audio formats are working, due to current kernel driver/codec constraints

I'm convinced Rock64 has great potential.
Note: you can purchase a 1Gb Rock64 board version, it will be enough to run Volumio comfortably.

Please report any issues here.


-- Gé --

Right now I'm using a 2A wall wort + USB to barrel connector. I really like this configuration because I can use the wall wort to charge my phone + eReader as well, so I don't have to carry around multiple chargers.

But it seems that when I'm using the PB it doesn't actually charge. Based on the battery capacity and lifetime of the PB I can't imagine it used more than ~1A, so it should be able to shunt current into the battery during use no?

Is there a little script or app that I can use to view power consumption / charge current etc... ?

Hi,

I've recently bought the couple of 4GB Rock64. One of them is not booting up.
When I plug the power, the green led starts to blink with approx. 10Hz rate, RK805-1 begins to heat and smell. I am afraid the problem is in RK805-1.

Unfortunately, RK805-1 parts seem to be unavailable on free market. I would have just replace the one and see what had happened.

Has anybody ever see the same? Is there any option except throw the device out?

Attached here are power supply and the board itself.

   

   

Hi all,

I have my Rock64 plugged into a gigabit switch along with my host computer. After adding the fix for the USB power problem I ran into an issue where ssh would frequently hang and I could not even run vi or remote X  tools. Even aptitude would hang when I attempted to search.

Anyway, I was able to fix the problem by installing ethtool and running ethtool eth0 -s advertise 0x008

This forces the board to only use 100Mbps instead of gigabit. My guess is that there may be something misconfigured in the MAC or PHY driver for this board, preventing large data transfers over gigabit (perhaps inter-packet spacing or something like that is wrong).

-Aaron

Will the new android support Bluetooth?

  Please can someone tell me what is going on? 
China Post Register Air Mail Tracking System

Parcel No.RY505116225CN tracking result
2017-10-13 10:19:54.0
logistic 订单已创建(速卖通平台)
2017-10-17 04:26:54.0
广东Shenzhen shipping center received
2017-10-17 04:59:38.0
广东Shenzhen shipping center customs scan
2017-10-17 05:24:39.0
已leaving 广东Shenzhen shipping center ，next station center
2017-10-17 07:23:49.0
Shenzhen export security scan
2017-10-17 16:03:17.0
Shenzhen center export customs scan (domestic transit )
2017-10-26 15:39:19.0
Shenzhen export security scan
2017-10-26 15:39:30.0
Shenzhen rejected ,remark (48)
2017-10-26 15:39:56.0
Shenzhen center export customs scan (domestic transit )

I have the Rock64 4GB version. Right now it's booting Debian Mate from the eMMC. What I would really like to do is put a DV-Mega Pi Hat on it and run it. Wondering if anyone has done this? What software did you use? If so would you kindly provide a link?
Thanks,
Mike
W3LNA
monitoring reflector 001

Official Fedora support is nearing the light of day from the good folks on the Fedora ARM team. Note to admins here, it may be time to add a Fedora Sub Forum on this site. :-)

If you are interested in running a pre-release version of Fedora 27 on your Pine64, here's what you need to do at this point in its development. Note, Fedora's philosophy eschews proprietary software as much as possible, so if upstream support isn't yet available, it won't be in Fedora. There's no graphical support yet, so you'll only be able to watch the OS boot on the serial console. On first boot, you can create a user, set the timezone, etc. Then you can log in. From there, once ethernet is established, you can SSH to the board.

Here are the steps as I best understand them. I'll update as needed:

*) Acquire a UART cable for using the serial console. Reference this resource:
http://linux-sunxi.org/Pine64#Serial_port_.2F_UART

*) Obtain one of the daily Fedora builds from Koji. I'd recommend one of either the Minimal or Server builds:
Minimal: https://koji.fedoraproject.org/koji/pack...geID=24072
Server: https://koji.fedoraproject.org/koji/pack...geID=24074
Make sure there's a green check mark by the item you intend to download, as that indicates that it was successfully built that day. Remember: This is pre-release software. Eventually you'll end up with a file named similar to this (the date will be different):
Fedora-Minimal-27-20171026.n.0.aarch64.raw.xz

*) Write the image to your microSD card. Determine the device name to which you'll be writing. /dev/sdb in this example.

Hi,

I read in other forum threads that it's possible to just have the boot image on the SD-card but then boot that actual OS from USB (or in most cases also from USB->msata connectors but in OpenHAB forum I didn't find a single thread about this.

Is nobody worried about sd-card corruption as openhab is writing logs and stuff constantly afaik.

Anyhow, what do I have to change (probably in boot partition) to actually boot from USB/msata SSD and how to copy OS Partition from card to ssd given I only have a windows machine (no linux with cardreader available).

Would greatly appreciate any help on this.

Best regards,

Marc

I'm trying to port the ODROID 16x2 LCD kit to the Rock64. The LCD functions with GPIO pins. However, since GPIO on the ODROID and the Rock64 differ, I'm trying to port the pin system. The GPIO shield for the ODROID LCD is unnecessary for porting this since the P2 block on the LCD board itself has its own pin scheme. There are only 16 pins in this scheme (of which only 10 are used). See pictures below for layout details...

The P2 block on the LCD shield. This block directly powers the LCD. GPIO input shield is a different set of pins.




The entire shield (notice the stacked boards). The pins on the green board directly control the LCD. The pin input information for the 16 pins on the green board are in the above image. "X" indicates the pin serves no purpose.


Would this involve modifying the code for the ODROID LCD controller program? The code and installation instructions for the ODROID-C (I assume any C model ODROID board) can be found here (https://wiki.odroid.com/accessory/displa...ld/c/start).

I'm new to GPIO so any clarification regarding my understanding of the pin system are appreciated.


Thanks.