Are there any SPDIF to optical cables which are suitable for the RockPro64 V2.1?

Is it supported in ALSA?

Is there a Linux driver for the MIPI CSI interface for the RK3399?

Or any documentation on the API to access the MIPI CSI interace and ISP of the RK3399?

Hi,
I am using Rockpro64 with Ubuntu18 image.
I have successfully done UART communication of rockpro through ttyS2 port(GPIO6,8) with my laptop.
No i have USB to serial(DB9) cable and i wanted to use one of the USB port of rockpro. I did try the same with 1500000 Baudrate but on my receiver side, i can see a garbage data is coming. I have tried different buadrates too but only garbage data is there.
Any suggestion? Can i use USB port for my serial communication?
Thanks.

I am sitting here with a totally useless cluster of over £1300 worth of pinepro64  because the wifi module has been disabled in the 7.8 + build. Many people buy these clusters for testing off corporate networks for prototyping and technology evaluation where bleeding edge open source software can be downloaded without the usual security screening. The wifi module was purchased to act as a bastion host to achieve this goal, but have been thwarted because Pine sell a wifi module that cant be supported in linux!!   

It would appear that there are issues with the PCIe interface and teh decision was taken to disable the wifi in favour keeping the PCIe stable.

I have no issues with this, but surely it would have been courteous  to give people the choice to enable wifi or PCIe? 

I too have a NVMe PCIe Disk to add but network access is *critical*.   

Question: Has *anybody* been able to get the wifi module working full stop on the rockPro64 linux builds ?

I have tried 20 builds in 2 days of testing with no luck ... even a 7.7 bionic-lxde arm64 dose not seem to work,

even with this build rfkill seems to only see the BT interface [# rfkill list] device 0 there is not device 1 for wifi

there is also no wlan0 interface to configure,
  

### Deeper Dive ###

### OS Drivers ###
From the kern.log it appears that the wifi device is being detected as chip ap6354 and allocated IRQ 3
There is an entry for Rockchip WiFi chip interface (V1.00)
I can not see any errors to indicate that there is a HW detection issue or a driver initialization issue for the wifi module

There is also a kernal command line entry registering a MAC address of e6:72:16:1c:22:0e on a uart8250 device which is not the RJ45 Ethernet device and has no registered vendor, but this may well be something to do with the boot process mounting to the emmc chip that holds the root partition.... (so it looks like a red herring)

What I do see is a statement that;
"of_get_named_gpiod_flags: can't parse 'WIFI,poweren_gpio' property of node '/wirelesspwlan[0]'

So I am wondering if the disabling has been triggered by a GPIO pin.

If anybody has any documentation on this wifi device HW design, driver and intended configuration it would be appreciated.

When I solve this I will post back to the forum.   


### HW ###
The Block diagram schematics seem to indicate that it shares the PCIe bus, although looking at the chips and pinouts it seems the module is supposed to be using;

UART interface for BlueTooth
SDIO interface for Wifi  

What this has to do with PCIe I dont know ... i am going to have to do some research here to understand how different bus \ signalling technologies can share a PCIe interface,

I bought the pine64 battery case and will be running it as a backup power supply for fluxuations/shutdown of the 12v supply coming from my car. 

The battery case came and has 2 copper wires just floating over the battery area, do these need to be attached to anything? They are "glued" together...

Also since the primary power will be coming from the DC usb, when I turn the car off will the battery automatically kick in and run the board?

I am using 4.4.132-1075-rockchip-ayufan kernel on Rockpro64 4GB board.

I boot from PCIe  SSD as roofs  and USB3 connecting a Seagate 2TB hard drive.

I recently notice this error:

I just wanted to share some messing around I've been doing to my rock64 today.  Currently I'm running the latest linux-rock64 from ayufan on Ubuntu Bionic.  I am using SPI to boot my system to a SSD I have plugged into the USB3 port.

Occasionally the u-boot has issues seeing the SSD properly and I have to reset the board a few times to get it to actually boot.  This wouldn't be an issue if it wasn't for the occasional power outage sending my system to an unresponsive state remotely since it is trapped in the bootloader without manual assistance.  Being willing to experiment I was considering trying to build u-boot myself, but I didn't get that far - I had noticed there was a new release flagged for build 1035 in ayufan's github.

Now I know I could just download the flash and do it that route, in fact that's what I had done last time I messed with the bootloader to get it to boot off the SSD in the first place with a pre-release at the time.  But I saw that the latest build was in the cache for APT and decided I would try and do it the linux way.

So this is where I realize that there's a bit of a problem with manually updating the bootloader through APT.  If I were to execute the command:

Hello,

Yesterday I just installed my Rock64Pro 2gb, and used the Libreelec with BelenaEtcher.

Everything is working fine.

But I have one problem, I can't get any sound out off the Rock.

In Kodi I have 3 options 2 regarding HDMI and 1 with Bluetooth All not working.

What I am trying to achieve is that the sound is going thru the 3,5 jack to my Edifier speakers.

Hope somebody can help, many thanks in advance.

Best regards Pepijn.
(From Holland)

Hey,

Been trying to build the android kernel for the ROCKPRO64, as I've wanted to add support for a wifi usb dongle I'm using.

Using Kernel Source from ayufan: https://github.com/ayufan-rock64/android-kernel

The build is failing with:

Hello,

I've got an SSD connected to my rock64 via USB3 and booting from it without issues.