R64.GPIO aims to re-implement RPi.GPIO for the Rock64, with the goal of 100% code compatibility with the original Raspberry Pi module.

The following functions are currently implemented and working:

• GPIO.setmode()
  
• GPIO.setwarnings()
  
• GPIO.setup()
  
• GPIO.output()
  
• GPIO.input()
  
• GPIO.cleanup()
  
• GPIO.PWM() (start, stop, ChangeFrequency, ChangeDutyCycle)
  
• GPIO.wait_for_edge()
  

• Interrupts (GPIO.event_detect)
  

• Download the entire "R64" folder from the repo, then place the "R64" folder in the same directory as the Python script you're working on.
  
• Within your script, substitute the normal "import RPi.GPIO as GPIO" line for "import R64.GPIO as GPIO". Syntax for implemented functions should be identical to RPi.GPIO.
  

• ROCK numbering is the default. I've created a reference spreadsheet of Rock64 pins, their functions, and their GPIO numbers, which you can find here: https://github.com/Leapo/Rock64-R64.GPIO...rence.xlsx
  
• BOARD numbering works exactly like it does in RPi.GPIO. Simply input a pin number, and the correct ROCK GPIO will be selected for you.
  
• BCM numbering attempts to emulate the physical layout of the Pi. This isn't perfect (some pins had to be mapped to the P5 header, can't use some pins with MicroSD, etc.), but I figured someone might find it useful.
  

I have been working with the incredibly talented NachoParker to get NextcloudPi running on a Rock64 Board.

I am happy to say I have succeeded!

I am using the March 26th nightly version of Armbian Stretch for the Rock64. This is a testing version of Armbian so there may be some time before it's "stable".

I used Nacho's command line install script to install all the bits and pieces for NextcloudPi. So far, it's working well. Still need to do some testing and validate all the various functions are working properly.

I'll keep working with Nacho to get his going. I plan on putting together a tutorial once I have someting viable.


Sent from my iPad using Tapatalk

Hi all!

I've just got a Rock64, burned the official image (minimal Debian), connected to the monitor and the keyboard, launched it and... realized I need an internet connection. For this I can use a laptop (Debian again) connected via WiFi, which has one Ethernet port free. I've got some general descriptions about bridging and routing in Linux having WiFi but nothing worked so far. Say, I have a difficulty to connect to the Ethernet port of the WiFi access point. I believe it's quite a common case. Could someone, please, help me and provide a real case example solving such problem?

Hello all.
I am testing out the Rock64 4gb. I've installed the community Ubuntu Mate and Debian, and in both none of my Wifi dongles work.
I've found a lot of threads about this, but don't seem to find a solution.
I've got 4 dongles, none work. Here is what I get from 2 simular ones that I want to use.

With lsusb it finds the dongles:
Bus 004 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter

This is what I get with lsusb -t

/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 480M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M

I downloaded this, but I have troubles getting it to work.
https://github.com/blahah/ralink_RT5370_linux_driver

I followed the instructions in the readme file. But when I do make, I get this message at the end.
  LD [M]  /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.mod.o
  LD [M]  /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.4.77-rockchip-ayufan-136'
cp -f /home/rock64/Desktop/ralink_RT5370_linux_driver-master/ralink_RT5370_linux_driver-master/os/linux/rt5572sta.ko /tftpboot
cp: cannot create regular file '/tftpboot': Permission denied
Makefile:388: recipe for target 'LINUX' failed
make: *** [LINUX] Error 1

Can someone please help me. I've been at it for a few days now. I'm no Linux master, so I don't know what I'm doing.
Thank you.
NicoD

sudo apt-get upgrade更新已安装的包 

sudo apt-get dist-upgrade升级系统 

会出现这样的错误。

每时每刻

I'm using windows 10, SDFomatter to erase SD (format adjustment ON). I have tried both etcher and Win32Diskimage. Only once did I get a bottable SD. I erased it because I wanted the desktop version. Since then, no image will boot up. I have ethernet hooked up, but it does show up an IPscanner, and I  my monitor nevers shows anything but a black screen.  What an I doing wrong?
I have burned/flashed all these images:

Armbian_5.41_Rock64_Debian_stretch_default_4.4.115_desktop
Armbian_5.41_Rock64_Ubuntu_xenial_default_4.4.115
artful-minimal-rock64-0.5.15-136-arm64
jessie-openmediavault-rock64-0.5.15-136-armhf
OMV_3_0_90_Pine64_4.13.10
stretch-mate-rock64-0.5.15-136-20171222-arm64

Without success. WHAT AM I DOING WRONG?...crimony!!!

Received my new clusterboard and OS-Pines today and have a few issues.

Mounting screw holes too small.  Since the board is MiniITX the mounting holes should be M3 (per the ATX spec), but they are much smaller.  The mounting screws on common MiniITX cases won't fit without modifying the holes.

SO-Pines won't reboot.  Already reported by @PeterKeuning.  On software reboot the SO-Pine powers down but does not restart.  At least most of the time...sometimes, randomly, it seems to work.

Power-on behavior is very inconsistent.  With less than 7 sockets populated everything seems to work consistently.  But with all 7 plugged in one or more modules does not start up.  The yellow NIC activity light on the "inactive" node does not flash and the green LED is also dark.  Also - when this happens - at least one of the other nodes has the green "heartbeet" LED on solid, though that module otherwise seems to be fine.

Clusterboard is powered from the on-board barrel jack using the "official" power brick.  I've moved the SO-Pine's around on the board to see if one of them is responsible, but it doesn't seem to follow any one module.  Software is Ayufun's xenial-minimal-sopine-bspkernel-0.7.19-118.

Also, any leads on a good working minimal Linux with mainline (or at least 4.4.x) kernel would be appreciated.  Looking for one that can be installed without having to hack the kernel modules to get network working (no need for video).

I have tried numerous and they all have had problems.

Armbian ( https://dl.armbian.com/pine64/) : just loads up to a certain point then starts just spewing "Call trace:" Even their Ubuntu image won't boot (Kernel panic).



The Ayunfan current image ( https://github.com/ayufan-pine64/linux-b...tag/0.7.19 ) boots, but requires additional files from an repo to install a desktop which is no longer available.

Older versions seem to get that Kernel Panic also.

The only one I can get up and running, is the one listed on the Wiki, but is not stable at all.

http://wiki.pine64.org/index.php/Pine_A6...essie_Mate


Another other suggestions?

So back when the pine 64 board was fresh off Kickstart I got the parts to build a tablet. Back then it was all really knew and a lot has changed and I haven’t really been apart of the community sense then. But I wanted to be able to run the touchscreen and hdmi at the same time back then. While I was trying to figure this out I read something on this forum about changing a file in the android os on my pine to run sound  out of hdmi and the 3.5mm jack. I did this and after the 3.5mm jack stopped working. This was over a year ago and I haven’t use the tablet much sense then. I now have a project that requires the use of the 3.5mm jack. I have spent the past hour tying to find that forum post to change the file but I cannot find it can anyone help me fix my jack?

Hi All, 

I have a rock64 running ayufan 0.5.15-136 with OMV 3. Works great so thanks to the pine64 team and the community - especially ayufan!

I am trying to get a docker image/container to work - https://github.com/haugene/docker-transmission-openvpn

This is a useful docker image that combines transmission and openvpn together but its not build for armhf so it needs to be built manually.

There is a armhf dockerfile that can be used to build an image for armhf and I have been able to use 'docker build' command to build the image on my rock64 but it doesn't work. I'm a total noob with docker so i was hoping to get some help.

I think the issue is the first command in the docker file - FROM resin/rpi-raspbiantretch

I think i need to change this with something that works for rock64. 

Any ideas?

thanks jata