| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
8 hours ago
» Replies: 6
» Views: 3,989
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
Yesterday, 08:23 AM
» Replies: 0
» Views: 47
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 150
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 70
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,547
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,169
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 235
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 160
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,640
|
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
06-27-2026, 02:43 PM
» Replies: 13
» Views: 18,833
|
|
|
| Unable to access other UART devices |
|
Posted by: alistair23 - 10-05-2018, 12:16 AM - Forum: Linux on PINE A64-LTS / SOPINE
- Replies (6)
|
 |
I have a SparkFun GPS module (https://www.sparkfun.com/products/11058) connected to my SOPINE board but I am unable to see any of the UART traffic.
I am running the latest mainline Arch kernel:
Linux alarm 4.18.0-2-ARCH #1 SMP Fri Sep 14 15:51:33 PDT 2018 aarch64 GNU/Linux
I have tried connecting it to both UART2 and UART4 with no luck.
Does anyone have any ideas on getting this to work? I see traffic when connecting it to the HiKey 96board. It should be outputting 3.3V which should work with UART2.
|
|
|
|
| cpu and case fan headers on PRO (NAS box) |
|
Posted by: dkebler - 10-04-2018, 03:56 PM - Forum: General Discussion on ROCKPRO64
- Replies (9)
|
|
I am assembling a recently arrived "new" NAS box. There are of course two fans (cpu, case). There is only one header labeled FAN (near gpio bus). I assume that if for the cpu fan and can be controlled by os/kernel? Where then should the case fan connect? There is another compatible two pin header labeled RIC nearby the fan header.
Also Is there any proper "motherboard" manual like one would get with a standard motherboard. The wiki has no detailed information on the board and it's connectors/headers.
|
|
|
|
| No WiFi |
|
Posted by: f4exb - 10-04-2018, 02:52 PM - Forum: RockPro64 Hardware and Accessories
- Replies (3)
|
|
Hello,
I have plugged in the optional WiFi/BT module but no joy. It is completely ignored by the system (Ubuntu Bionic from http://wiki.pine64.org/index.php/ROCKPro....04_Bionic):
Code: uname -a
Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routable configured
sudo lshw -c network
*-network
description: Ethernet interface
physical id: 7
logical name: eth0
serial: 32:cb:11:5d:df:5e
size: 100Mbit/s
capacity: 1Gbit/s
capabilities: ethernet physical tp aui bnc mii fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=st_gmac driverversion=March_2013 duplex=full ip=192.168.1.34 link=yes multicast=yes port=MII speed=100Mbit/
Can you please advise?
Brgds, Edouard.
|
|
|
|
| Most stable Linux rom and 1080p support? |
|
Posted by: Nelly - 10-04-2018, 01:05 PM - Forum: Linux on Rock64
- Replies (2)
|
|
Hello there are many Linux roms available for the rock64, can someone please advise me on the most stable Linux rom? Can Linux support 1080p video yet? Not just though kodi or whatever, I want to be able to use my browser and log in to steaming services like Skygo for example. Like I would on desktop, thanks.
|
|
|
|
| writing dts overlay for mcp2515 |
|
Posted by: Hydrocactus - 10-04-2018, 09:23 AM - Forum: Linux on Rock64
- No Replies
|
|
Hi there I'm trying to write a dts file to make "pican2" mcp2515 based hat working on armbian, I've wrote a dts file, compiled it, and I've put it in /boot/overlay-user/.
It's not working.
I've tried hard, but now as I'm stuck and because I'm a noob in devices-tree world I come here to ask for help, so please take a look.
here is my dts file:
Code: /dts-v1/;
/plugin/;
/ {
compatible = "rockchip,rk3328", "pine64,rock64";
fragment@0 {
target-path = "/spi@ff190000";
//target = <&spi0>;
__overlay__ {
status="okay";
spidev@0{
status = "disabled";
};
spidev@1{
status = "disabled";
};
};
};
/* the interrupt pin of the can-controller */
fragment@1 {
target-path = "/pinctrl/gpio3@ff240000";
//target = <&gpio3>;
__overlay__ {
can0_pins: can0_pins {
rockchip,pins = <0 7 0 &pcfg_pull_none>;
//phandle = <1>;
};
};
};
/* the clock/oscillator of the can-controller */
fragment@2 {
target-path = "/";
__overlay__ {
/* external oscillator of mcp2515 on SPI0.0 */
can0_osc: can0_osc {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <16000000>;
};
};
};
/* the spi config of the can-controller itself binding everything together */
fragment@3 {
target-path = "/spi@ff190000";
//target = <&spi0>;
__overlay__ {
/* needed to avoid dtc warning */
#address-cells = <1>;
#size-cells = <0>;
can0: can0@0 {
//phandle = <1>;
reg = <0>;
compatible = "microchip,mcp2515";
pinctrl-names = "default";
pinctrl-0 = <&can0_pins>;
//pinctrl-0 = "/pinctrl/gpio3@ff240000/can0_pins/";
spi-max-frequency = <10000000>;
interrupt-parent = <&gpio3>;
//interrupt-parent = "/pinctrl/gpio3@ff240000";
interrupts = <7 0x2>; // 7 2
//clocks = "/can0_osc";
clocks = <&can0_osc>;
};
};
};
};
and here is what I can read in my dmesg:
Code: [ 0.199580] bus: 'spi': registered
[ 0.199591] device class 'spi_master': registering
[ 0.215439] device: 'ff190000.spi': device_add
[ 0.215471] bus: 'platform': add device ff190000.spi
[ 0.215560] PM: Adding info for platform:ff190000.spi
[ 2.069101] bus: 'spi': add driver cros-ec-spi
[ 2.069297] device class 'spi_transport': registering
[ 2.069329] device class 'spi_host': registering
[ 2.070797] bus: 'spi': add driver m25p80
[ 2.070861] device class 'spidev': registering
[ 2.070890] bus: 'spi': add driver spidev
[ 2.070956] bus: 'platform': add driver rockchip-spi
[ 2.071145] bus: 'platform': driver_probe_device: matched device ff190000.spi with driver rockchip-spi
[ 2.071162] bus: 'platform': really_probe: probing driver rockchip-spi with device ff190000.spi
[ 2.071495] rockchip-spi ff190000.spi: no init pinctrl state
[ 2.071552] rockchip-spi ff190000.spi: no sleep pinctrl state
[ 2.071566] rockchip-spi ff190000.spi: no idle pinctrl state
[ 2.071795] rockchip-spi ff190000.spi: no high_speed pinctrl state
[ 2.071820] device: 'spi32766': device_add
[ 2.072075] PM: Adding info for No Bus:spi32766
[ 2.072326] device: 'spi32766.0': device_add
[ 2.072362] bus: 'spi': add device spi32766.0
[ 2.072582] PM: Adding info for spi:spi32766.0
[ 2.072661] rockchip-spi ff190000.spi: chipselect 0 already in use
[ 2.072675] spi_master spi32766: spi_device register error /spi@ff190000/flash@0
[ 2.072692] spi_master spi32766: Failed to create SPI device for /spi@ff190000/flash@0
[ 2.072709] driver: 'rockchip-spi': driver_bound: bound to device 'ff190000.spi'
[ 2.072758] bus: 'platform': really_probe: bound device ff190000.spi to driver rockchip-spi
[ 8.643523] bus: 'spi': add driver mcp251x
[ 8.643560] bus: 'spi': driver_probe_device: matched device spi32766.0 with driver mcp251x
[ 8.643570] bus: 'spi': really_probe: probing driver mcp251x with device spi32766.0
[ 8.643678] mcp251x spi32766.0: no pinctrl handle
[ 8.646051] mcp251x spi32766.0: Looking up vdd-supply from device tree
[ 8.646071] mcp251x spi32766.0: Looking up vdd-supply property in node /spi@ff190000/can0@0 failed
[ 8.648100] mcp251x spi32766.0: Looking up xceiver-supply from device tree
[ 8.648120] mcp251x spi32766.0: Looking up xceiver-supply property in node /spi@ff190000/can0@0 failed
[ 8.661924] mcp251x: probe of spi32766.0 rejects match -19
|
|
|
|
| Multiarch liveusb? |
|
Posted by: graphical - 10-03-2018, 02:21 AM - Forum: Linux on Rock64
- No Replies
|
|
Hello all,
I got a really cool idea and I need to be tuned down a bit.
I'm making myself a bootable usb drive.
Thing is, I want to know if it is even possible to have ONE bootable usb drive for both ARM64 and x64 at once.
Maybe there is some magical™ bootloader that would work on arm as well as x64 from a single compile?
I've been googling this quite a bit, but nothing relevant has come up. This usually means that I'm acting a fool.
Putting this in the linux section, because I want to know if GRUB is even available for the Rock64.
Again, thank you for your time.
|
|
|
|
benefits of eMMC? |
|
Posted by: SirSkorpan - 10-01-2018, 02:20 PM - Forum: RockPro64 Hardware and Accessories
- Replies (5)
|
|
I'm considering buying a RockPro64 to use as a NAS and general server, I saw that one could buy eMMC modules to use as internal memory for the board. I have a few questions here:
- What is the benefit of using eMMC rather than SD card? Speed, longer lifetime or the storage?
- How is the eMMC module attached to the board? I couldn't identify an obvious slot or similar connection.
- What is the purpose of the USB adapter, is it to "burn" the OS image to the eMMC or do you need it to attach the eMMC to the board?
|
|
|
|
|
