| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,679
» Latest member: Gett1272
» Forum threads: 16,253
» Forum posts: 117,171
Full Statistics
|
| Latest Threads |
Are you interested in a n...
Forum: General Discussion on Pinebook Pro
Last Post: WEF
Yesterday, 02:33 PM
» Replies: 2
» Views: 2,965
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
Yesterday, 11:18 AM
» Replies: 3
» Views: 281
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
Yesterday, 07:29 AM
» Replies: 0
» Views: 59
|
black cursos background
Forum: General Discussion on PineTab
Last Post: polrus
11-11-2025, 04:07 PM
» Replies: 0
» Views: 51
|
slight bumps causing phon...
Forum: PinePhone Pro Hardware
Last Post: JadenSki
11-11-2025, 02:05 PM
» Replies: 2
» Views: 93
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
11-11-2025, 02:01 PM
» Replies: 10
» Views: 12,481
|
Switching cameras on PPpr...
Forum: Mobian on PinePhone
Last Post: biketool
11-11-2025, 10:44 AM
» Replies: 0
» Views: 48
|
Battery connector dead
Forum: PinePhone Hardware
Last Post: mdk
11-11-2025, 10:05 AM
» Replies: 3
» Views: 2,372
|
No touch KB after update(...
Forum: Mobian on PinePhone
Last Post: biketool
11-11-2025, 09:45 AM
» Replies: 3
» Views: 180
|
compass pdf link expired:...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-10-2025, 12:39 PM
» Replies: 4
» Views: 297
|
|
|
| SPI Interface questions |
|
Posted by: bencrosby - 01-02-2018, 05:40 PM - Forum: Rock64 Hardware and Accessories
- Replies (9)
|
 |
Hi folks,
I'm somewhat confused by the SPI interfaces in the RK3328 and thus their application in the ROCK64.
I've dug through all the documentation. It appears that there are three SPI interfaces in the RK3328, per Pg. 483 of the technical reference manual.
Code: INTERFACE CLOCK RXD TXD CSN0 CSN1
SPI0 (m0) clkm0 : GPIO2B0 rxdm0 : GPIO2B2 txdm0 : GPIO2B1 csn0m0 : GPIO2B3 csn1m0 : GPIO2B4
SPI1 (m1) clkm1 : GPIO3C7 rxdm1 : GPIO3D0 txdm1 : GPIO3D1 csn0m1 : GPIO3D2 csn1m1 : GPIO3D3
SPI2 (m2) clkm2 : GPIO3A0 rxdm2 : GPIO3A2 txdm2 : GPIO3A1 csn0m2 : GPIO3B0 N/A
In ROCK64_Schematic_v2.0_20171019.pdf and the ROCK64 Pi2 Bus diagram....
Pi2 Bus Pin 24 is marked as "SPI_CSN0_M2", Pin 26 is marked as "SPI_CSN1_M0"
This is the first thing that confused me. Why do we have only one CS belonging to two different SPI interfaces on the header ?
The SPI2 (m2) Interface is exposed on the header. It has only on CS, and can only have one device on the bus.
It appears that bus m2 is the same one used for the ROCK64 on-board 128M flash chip (U1) per page 6 of the schematics.
Question 1: If so, how does one use the SPI interface on the Pi-2 bus without also addressing the onboard 128M Flash ?
Question 2: What was the purpose of exposing SPI_CSN1_M0 to the header when the rest of SPI_M0 is inaccessible ?
As far as I can tell, interface M0 and M1 are not used. In fact, it may even be that these interfaces aren't available on the BGA - I can't find them on the Ball Map.
I am wondering if future versions of the ROCK64 will make any changes? If so, is there a forum or suitable place to send suggestions ?
Suggestion: If possible, populate the header with a usable SPI bus e.g. m0 or m1, and provide both cs lines, e.g.
Pin 19: SPI_TXD_Mx
Pin 21: SPI_RXD_Mx
Pin 23: SPI_CLK_Mx
Pin 24: SPI_CSN0_Mx
Pin 26: SPI_CSN1_Mx
Cheers.
|
|
|
|
| pi case conversions for rock64 |
|
Posted by: sandradabo00 - 01-01-2018, 12:34 PM - Forum: Rock64 Hardware and Accessories
- Replies (8)
|
 |
Hello all,
I am looking for a case for rock64 board that is available in Europe. There does not seem to be any.
Has anyone managed to adapt an existing raspberry pi case for rock64 ? I would like to make a media center so it should be good looking (and cheap).
Any guides out there ?
Thanks
|
|
|
|
| Kubernetes on SoPine cluster part.1 |
|
Posted by: maya.b - 12-31-2017, 05:08 AM - Forum: Clusterboard
- Replies (3)
|
 |
So this is a quick guide on how I got Kubernetes installed and running on 5 nodes on a prototype SoPine clusterboard. This can also work on rock64's, pine64(+)/LTS or anything else really. I'm assuming you already know how to flash OS SD card images using your favourite host OS, and can configure a router, in particular assigning manual DHCP addresses to hosts.
This isn't step by step, and if you need clarification, then perhaps go learn about whatever it is first. This is not a beginner's guide.
Background:
I recently got the book "Kubernetes Up & Running" (KUAR) by Hightower, Burns & Beda from O'Reilly. It came out in September 2017 so it's fairly current, although with all tech books, there are some things already out of date.
I read the intro and chapter 1 - nice and informative.
Chapter 2 - "you may want to start expriementing" it suggested. Uhhm, yes. "You should use an online service offering" it advised. Uhmm, if I have to ... "If you're really want to set it up yourself ... appendix A has a guide" it revealed. I skipped the rest of Chapter 2 for now. Chapters 3 through Appendix A, I'll get back to later as well
NB* THIS IS SO FAR FROM PRODUCTION READY.
The steps that follow are a rough paraphrase of Appendix A in the KUAR book with a few changes (ie that out of date already stuff)
Step 1- Get hardware. - Two or more sopines
- sopine clusterboard (cheats power cabling, network cabling (has built in GigE ethernet switch), cable management and all the other hassles of DIY clusters)
Step 2- make a bunch of OS SD cards- I used an armbian 5.37 BSP xenial server build, any xenial build should work but stick with the minimal builds as you won't need most of what's in minimal, nevermind anything else
Step 3- network config - Rather than installing DHCP tools on the host node, I just plugged them in an booted each sopine up sequentially, and assinged them hosts sopine[0..4] and on my router gave them IP addresses nnn.nnn.nnn.200 through 204 (where n is whatever subnet used on your router. eg 192.168.1.200 or 10.10.10.200)
- The book assumes the cluster will be isolated and hidden from the world so there are some extra network forwarding steps and configs I completely ignored as the clusterboard has it's own switch directly connected to the 'net and all nodes can see the world. Again this is *not* a production ready setup, where you'd likely have one exposed node, and all your worker nodes hidden/protected in a vlan or simiar. (Have I mentioned this is *not* a production ready setup?)
Step 4- Install Kubernetes stuff- (optional) install cssh(X) - Cluster SSH lets you blow up numerous systems at once by ssh'ing into all of them simultaneously and running things all at once. Since I haven't bothered (yet) with config management to setup the sopines, this is even more efficient #BadDevOps than ssh'ing into them individually way of doing things. (Thank you Xalius for introducing this to me!) (csshX is the OSX brew version)
- install docker.io - this is the default container engine
- install kubernetes package encryption key:
Code: curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
- Add repo to your repo's list
Code: echo "deb http://apt.kubernetes.io/ kubernetes-xenial main" >> /etc/apt/sources.list.d/kubernetes.list
- Update and upgrade the nodes
- install actual kubernetes stuff
Code: apt install -y kubelet kubeadm kubectl kubernetes-cni
- this installed version 1.9 on my sopines
Step 5- Setup up the cluster!- On the master node (sopine0 in my case)
Code: kubeadm init --pod-network-cidr 192.168.1.0/24 --apiserver-advertise-address 192.168.1.200
- Make sure to use the correct network range as you may not be using the same subnet as I. This will take a while. It will also generate the <token> you need to initialise the slave nodes and will actually print out the command for the slave nodes to join the cluster
- on the slave nodes (sopine[1..n])
Code: kubeadm join --token=<token> 192.168.1.200:6443 --discovery-token-ca-cert-hash sha256:<hash>
- if it all played nice then to see your embryonic Kubernetes cluster details
That's it for now, there are more things to do of course but that's what it takes to get started with (a non production ready) kubernetes cluster on a sopine cluster board.
|
|
|
|
| Interfacing display |
|
Posted by: bencrosby - 12-31-2017, 03:26 AM - Forum: Rock64 Hardware and Accessories
- Replies (1)
|
 |
Hi folks, just doing some hunting around for information...
I note that the GPIO on the Rock64 is supposed to be capable of emulating Pi2.
I also note that some of the pins are not mapped the same way.
I was using a Pi2 with a Parallel RGB (DPI Mode 2) display. This makes use of pins 11, 29, and 31 which are all "NC" pins on the Rock64.
I am therefore assuming the Rock64 is incapable of interfacing with a RGB 16Bit 565 type display ?
Cheers
Ben
|
|
|
|
Constant crash Xenial minimal - help much appreciated |
|
Posted by: freeloader - 12-30-2017, 09:56 AM - Forum: Linux on Rock64
- Replies (8)
|
 |
Hi guys,
First of: love the Rock64 so far, very happy running the ayufan Xenial minimal.
I was a bit hesistant about buying the Rock64 due to it being a relatively new device, but was convinced due to what seems like a vibrant user community being built here. The community pages proved to be very helpful in setting up the device, thanks for that!
I did a search in the forum on my specific issue and could not find a direct solution - apologies in advance if it turns out to be a rookie / easy mistake. I have working knowledge from tinkering with Linux over the past 15 years, but am definitely not an expert.
My setup:
- Rock 64 on the official power supply (running on a US to EU power converter however).
- Running Ayufan Xenial minimal on a 16GB micro SD card.
- Aukey USB powered hub: https://www.amazon.de/dp/B00QM89U4G/ref=...11_TE_dp_1
- Three Seagate Expansion Portable 4TB drives linked to the USB hub: https://www.amazon.de/dp/B017KE8OG0/ref=...11_TE_dp_1
- Very limited software installed (Docker, vsftp)
What happened:
I tried setting up my three external harddrives in RAID 0, following this tutorial:
https://forum.pine64.org/showthread.php?tid=5231
In the middle of the tutorial, the device crashed (no error message on screen through putty).
I connected the Rock64 to a monitor (figured at first there was a problem with the network connection) and saw it crashing in 'real time' (while I was not taking any user actions). I took a few pictures (attached to this post). I looked at syslog and the last error there is from a few hours before the crashed. Happy to post any other logs.
In essence, it seems there are a few read/write errors on my external disks and then the device crashed. I plugged out the USB hub and the crashing stopped, so the error is likely connected to the drives.
I took a good look at one of the overview forum posts (https://forum.pine64.org/showthread.php?tid=4760) and I think my issue might be linked to undervoltage. Is there any way to check that? I thought my powered HUB was strong enough to handle all three drives, but please correct me if I'm wrong.
Logs:
![[Image: 1.jpg]](https://preview.ibb.co/cCv14w/1.jpg)
![[Image: 2.jpg]](https://preview.ibb.co/cxFOHG/2.jpg)
![[Image: 3.jpg]](https://preview.ibb.co/bSFvWb/3.jpg)
Any help appreciated!
|
|
|
|
Rock64 and ALSA (Multichannel and HighRes) |
|
Posted by: tweeKpot - 12-29-2017, 03:45 PM - Forum: Linux on Rock64
- No Replies
|
 |
Hello, everyone!
Merry Christmas and Happy New Year!
I'm looking for a device for music streaming.
I'd like to output sound via HDMI port to my AVR.
Can anybody confirm, that HighRes and surround sound are output correctly using any of the supported distribution? Ubuntu/Debian, LibreELEC, Volumio?
Maybe someone can post outputs of aplay -l command, or even try to do speaker-test with different samplerates and channel numbers?
Does your AVR shows correct samplerate and channels? Are the channels mapped correctly?
I've tried such streaming using HDMI output of my HP ProBook 4530s with Ubuntu 16.04.
Installed upmpdcli and mpd and everything works as expected. AVR indicates correct sample rates and channel number with any source I throw to it. 44.1/48/88.2/96/176.4/192kHz, 2ch or 6ch.
I also have CubieBoard2 and Tanix TX5 Pro devices.
Both devices can only output 2 or 8ch, which is not perfect. I have to do channel assignments via asound.conf, and as a result sound is always output as 8ch.
RPi 3 cannot output anything higher, than 2ch/48kHz.
Rock64 is my last hope to have small small music network streaming device =)
Thanks for your help!
|
|
|
|
ROCK64 emmc |
|
Posted by: Diogenes08 - 12-29-2017, 11:49 AM - Forum: Getting Started
- Replies (2)
|
 |
I recently purchased and am awaiting both a Pine64-LTS and a ROCK64, both with emmc modules. After purchasing, I realized that I had not purchased the emmc to usb adapter. This is my fault, but I have been looking into my options in the meantime.
Here is the information that I have gathered, though I may have gotten some things wrong(that is the first part of my question, and leads directly to the second.)
1. On the LTS, there are images I can write to SD, and then install to emmc.
2. These installers are not available on the ROCK(if they are, my question basically ends here, as I can install to emmc without needing to wait for the adapter.)
The second part of my question, which assumes #2 above is true, is whether I can put the emmc into the LTS, write a ROCK image, and just put the emmc into the ROCK?
|
|
|
|
|