| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Satellite antenna
Forum: Community and Events
Last Post: biketool
Yesterday, 02:46 PM
» Replies: 2
» Views: 379
|
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
10-25-2026, 04:11 AM
» Replies: 5
» Views: 14,848
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
10-23-2026, 12:14 PM
» Replies: 25
» Views: 26,018
|
Alpha One - no connectivi...
Forum: Getting Started
Last Post: Dabdarklighter
10-22-2026, 03:51 PM
» Replies: 1
» Views: 1,146
|
Article: The Advantages o...
Forum: General
Last Post: zetabeta
10-20-2026, 02:38 PM
» Replies: 2
» Views: 326
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
10-19-2026, 12:27 PM
» Replies: 22
» Views: 21,456
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
10-19-2026, 10:01 AM
» Replies: 25
» Views: 16,214
|
Article: Will Linux phone...
Forum: General
Last Post: amosbatto
10-19-2026, 09:52 AM
» Replies: 11
» Views: 1,445
|
Login issues
Forum: PineTab Hardware
Last Post: Corkonian
10-17-2026, 02:34 AM
» Replies: 2
» Views: 447
|
Rii mini 4 keyboard and t...
Forum: PinePhone Accessories
Last Post: Flymoon
10-15-2026, 08:04 AM
» Replies: 3
» Views: 5,950
|
|
|
| strange behaviour on newer kernel |
|
Posted by: tuxd3v - 10-05-2018, 10:44 PM - Forum: Linux on RockPro64
- Replies (3)
|
 |
Hello,
I noticed that after upgrade to:
linux-image-4.4.154-1122-rockchip-ayufan-g7859b9b904a9 linux-headers-4.4.154-1122-rockchip-ayufan-g7859b9b904a9 linux-firmware-image-4.4.154-1122-rockchip-ayufan-g7859b9b904a9
My Fan stop and start, almost by itself..
Does anyone is experiencing the same?
I am um the bionic image..
|
|
|
|
| USB 2.0 OTG port |
|
Posted by: gautham159 - 10-05-2018, 11:22 AM - Forum: Ubuntu
- Replies (3)
|
|
I have rock64 board, flashed Ubuntu 18.04 Bionic minimal 64bit Image booting off of sd-card. Updated rk3328-rock64.dts
Code: &usb20_otg {
dr_mode = "**peripheral**";
status = "okay";
};
compiled and updated rk3328-rock64.dtb. Connected usb (type A) cable, rock64 USB 2.0 OTG port - latop. Laptop couldn't detect the usb-serial connection though.
Is rock64 OTG port working? am I missing any steps?
Any suggestion is very much appreciated because otg support is the blocker!!
Thank you in advance,
Gautham
|
|
|
|
| Flashing android to eMMC from linux sd card boot |
|
Posted by: nlem - 10-05-2018, 07:24 AM - Forum: Android on RockPro64
- Replies (1)
|
|
This is a method that worked to install android 8.1 onto emmc without using the emmc to SD card adaptor.
It also worked when using the Android tools did not.
Someone else may find this useful
=== Flashing Android to eMMC from Linux SD Boot (ROCKPro64)===
This method enables installing android to emmc using dd method without an emmc adaptor.
Can also be an alternate method if other methods are unsuccesful
Install Linux to an SD Card (Verified with bionic but may work with others).
Insert SD and empty eMMc (eMMc card must be empty so that ROCKPro64 boots off SD card).
(If necessary, emmc can be cleared using android tools linked below)
Boot Linux
Download desired dd android image from pine64 using curl (curl http://link_to_rockpro64_image.img.xz --output AndroidImage.img.xz)
Extract android image using unxz (unxz AndroidImage.img.xz)
Verify that emmc is visible by typing sudo fdisk -l | less.
eMMc should be shown as /dev/mmcblk1 with the correct size
Write android image to emmc using dd (sudo dd if=./AndroidImage.img od=/dev/mmcblk1)
Wait for dd to finish. (if screen turns off give it another 10 minutes and assume its done).
Unplug power, remove sd card.
Plug power back in and enjoy android.
Thanks to lucasz for helping out.
|
|
|
|
| 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
|
|
|
|
|
