Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,501
» Latest member: jakestopher
» Forum threads: 16,203
» Forum posts: 116,908

Full Statistics

Latest Threads
Goolge banning Sideloaded...
Forum: General Discussion of PinePhone Pro
Last Post: zetabeta
8 hours ago
» Replies: 1
» Views: 367
Question about battery dr...
Forum: General Discussion on PineTime
Last Post: jakestopher
9 hours ago
» Replies: 0
» Views: 15
What's stopping you from ...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
Yesterday, 11:48 PM
» Replies: 8
» Views: 842
Pinephone (Pro) Keyboard ...
Forum: PinePhone Accessories
Last Post: zetabeta
Yesterday, 06:06 AM
» Replies: 3
» Views: 2,244
keyboard pogo pins part n...
Forum: General Discussion on PineTab
Last Post: starpp
Yesterday, 04:34 AM
» Replies: 0
» Views: 475
google will take control ...
Forum: General
Last Post: zetabeta
08-25-2025, 03:14 PM
» Replies: 22
» Views: 9,954
Booting Issues
Forum: PineNote Software
Last Post: serenopolveroso
08-25-2025, 11:14 AM
» Replies: 19
» Views: 5,618
PINETAB-V doesn't boot.
Forum: Getting Started
Last Post: Woazboat
08-23-2025, 02:58 PM
» Replies: 1
» Views: 807
PinePhone Pro: Camera App...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-22-2025, 11:23 PM
» Replies: 3
» Views: 2,852
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-22-2025, 11:19 PM
» Replies: 9
» Views: 1,647

 
  Rock64 does not boot - SPI problem [resolved]
Posted by: csharpy - 03-21-2018, 02:26 AM - Forum: General Discussion on ROCK64 - Replies (7)

Hi everybody,

I need some help with my rock64 - it does not boot up. I purchased it second hand, the previous owner said that since he tried to re-flash the SPI it does not come up again. 

I attached a serial console to watch the boot process and now I‘m stuck. Here are the boot messages (appearing in an eternal loop):

Resetting CPU ...

DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT

U-Boot SPL 2017.09-ga0a2b48 (Feb 19 2018 - 18:43:53)
setup_ddr_param  1
booted from SPI flash
Trying to boot from SPI
"Synchronous Abort" handler, esr 0x02000000
ELR:     200000
LR:      1890
x 0: 0000000000400000 x 1: 0000000000000000
x 2: 0000000000200000 x 3: 0000000000000180
x 4: 0000000000000002 x 5: 000000000000ace4
x 6: 000000000000003b x 7: 00000000ff190000
x 8: 0000000000000b8c x 9: 000000002ed96880
x10: 00000000005ffcac x11: 000000000000dc98
x12: 0000000000000b67 x13: 0000000000000b90
x14: 00000000005ffd0c x15: 000000000000dc98
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000005ffea0 x19: 000000000000d498
x20: 000000000000d480 x21: 0000000000000000
x22: 00000000005ffe70 x23: 00000000005ffe58
x24: 000000000000b50b x25: 000000000000b4f3
x26: 000000000000d000 x27: 00000000deadbeef
x28: 0000000000000430 x29: 00000000005ffde0

Resetting CPU ...

...

All attempts of erasing or re-flashing the SPI as described here do not work. The rock64 does not seem to come to the point where it would be able to read from the micro sd card. 

Does anybody have a hint for me? Do I need a eMMC card to boot from? Or are there ways of erasing the SPI flash memory through the GPIO pins?

Any help is greatly appreciated! Thanks!


  Rock64 Starter Kit Help
Posted by: chaust - 03-20-2018, 07:18 PM - Forum: General Discussion on ROCK64 - Replies (7)

Hi, I am planning to buy Rock64 4GB, I decided to opt for this because of the better speeds than the raspberry pi.

Would you think this a good starter pack for emulation and media center purposes? What else do I need, or what I don't need? 

Thanks!

[Image: R12fXbs.png]


  External hard drive problem
Posted by: k8Va - 03-20-2018, 06:53 PM - Forum: Linux on Rock64 - Replies (17)

I just got my ROCK 64 with the jessie-openmediavault-rock64-0.6.25-193-arm64.img image from https://github.com/ayufan-rock64/linux-b...tag/0.6.25 

But the external hard (http://en.sharkoon.com/product/1685/10394#specs) drive isnt recognized.

What is going on? The hard drive works fine with Openmediavault on raspberry pi & OdroidXU4.

Code:
root@rock64:~# sudo fdisk -l

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mtdblock0: 4 MiB, 4161536 bytes, 8128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mtdblock1: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
GPT PMBR size mismatch (4458495 != 15359999) will be corrected by w(rite).

Disk /dev/mmcblk1: 7.3 GiB, 7864320000 bytes, 15360000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 824DA7D1-B7E7-49CA-A273-69A1E8B9785F

Device          Start      End  Sectors  Size Type
/dev/mmcblk1p1     64     8063     8000  3.9M Linux filesystem
/dev/mmcblk1p2   8064     8191      128   64K Linux filesystem
/dev/mmcblk1p3   8192    16383     8192    4M Linux filesystem
/dev/mmcblk1p4  16384    24575     8192    4M Linux filesystem
/dev/mmcblk1p5  24576    32767     8192    4M Linux filesystem
/dev/mmcblk1p6  32768   262143   229376  112M Microsoft basic data
/dev/mmcblk1p7 262144 15359966 15097823  7.2G Linux filesystem


At around 900 seconds I powered off and on the HD...

Code:
root@rock64:~# dmesg | grep usb
[    0.614193] usbcore: registered new interface driver usbfs
[    0.614793] usbcore: registered new interface driver hub
[    0.615433] usbcore: registered new device driver usb
[    1.161801] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply from device tree
[    1.161918] vcc_host1_5v: could not add device link phy-ff450000.syscon:usb2-phy@100.0 err -2
[    1.162519] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply from device tree
[    1.162629] vcc_host1_5v: could not add device link phy-ff450000.syscon:usb2-phy@100.1 err -2
[    1.163102] rockchip-usb2phy ff450000.syscon:usb2-phy@100: GPIO lookup for consumer otg-vbus
[    1.163120] rockchip-usb2phy ff450000.syscon:usb2-phy@100: using device tree for GPIO lookup
[    1.163139] of_get_named_gpiod_flags: can't parse 'otg-vbus-gpios' property of node '/syscon@ff450000/usb2-phy@100[0]'
[    1.163155] of_get_named_gpiod_flags: can't parse 'otg-vbus-gpio' property of node '/syscon@ff450000/usb2-phy@100[0]'
[    1.163171] rockchip-usb2phy ff450000.syscon:usb2-phy@100: using lookup tables for GPIO lookup
[    1.163186] rockchip-usb2phy ff450000.syscon:usb2-phy@100: lookup for GPIO otg-vbus failed
[    1.163201] rockchip-usb2phy ff450000.syscon:usb2-phy@100: vbus_drv is not assigned
[    1.164774] rockchip-u3phy ff470000.usb3-phy: GPIO lookup for consumer vbus-drv
[    1.164793] rockchip-u3phy ff470000.usb3-phy: using device tree for GPIO lookup
[    1.164811] of_get_named_gpiod_flags: can't parse 'vbus-drv-gpios' property of node '/usb3-phy@ff470000[0]'
[    1.164829] of_get_named_gpiod_flags: can't parse 'vbus-drv-gpio' property of node '/usb3-phy@ff470000[0]'
[    1.164843] rockchip-u3phy ff470000.usb3-phy: using lookup tables for GPIO lookup
[    1.164858] rockchip-u3phy ff470000.usb3-phy: lookup for GPIO vbus-drv failed
[    1.164872] rockchip-u3phy ff470000.usb3-phy: vbus_drv is not assigned
[    1.165945] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tree
[    1.165965] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in node /usb3-phy@ff470000/utmi@ff470000 failed
[    1.166405] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tree
[    1.166427] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in node /usb3-phy@ff470000/pipe@ff478000 failed
[    1.168184] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized successfully
[    1.601869] usbcore: registered new interface driver udl
[    2.252837] usbcore: registered new interface driver cdc_ether
[    2.252900] usbcore: registered new interface driver rndis_host
[    2.255119] phy phy-ff470000.usb3-phy.2: u3phy u2 power on
[    2.255145] phy phy-ff470000.usb3-phy.3: u3phy u3 power on
[    2.256290] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree
[    2.256303] dwc2 ff580000.usb: Looking up vusb_d-supply property in node /usb@ff580000 failed
[    2.256318] ff580000.usb supply vusb_d not found, using dummy regulator
[    2.256418] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree
[    2.256429] dwc2 ff580000.usb: Looking up vusb_a-supply property in node /usb@ff580000 failed
[    2.256438] ff580000.usb supply vusb_a not found, using dummy regulator
[    2.269039] dwc2 ff580000.usb: DWC OTG Controller
[    2.269106] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[    2.269153] dwc2 ff580000.usb: irq 43, io mem 0xff580000
[    2.269451] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.269461] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.269469] usb usb1: Product: DWC OTG Controller
[    2.269477] usb usb1: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 dwc2_hsotg
[    2.269485] usb usb1: SerialNumber: ff580000.usb
[    2.339882] ehci-platform ff5c0000.usb: EHCI Host Controller
[    2.340258] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[    2.340412] ehci-platform ff5c0000.usb: irq 44, io mem 0xff5c0000
[    2.346124] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[    2.346421] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    2.346432] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.346440] usb usb2: Product: EHCI Host Controller
[    2.346448] usb usb2: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 ehci_hcd
[    2.346455] usb usb2: SerialNumber: ff5c0000.usb
[    2.348661] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[    2.348982] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[    2.349160] ohci-platform ff5d0000.usb: irq 45, io mem 0xff5d0000
[    2.404377] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    2.404387] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.404395] usb usb3: Product: Generic Platform OHCI controller
[    2.404404] usb usb3: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 ohci_hcd
[    2.404411] usb usb3: SerialNumber: ff5d0000.usb
[    2.407569] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    2.407579] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.407587] usb usb4: Product: xHCI Host Controller
[    2.407595] usb usb4: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 xhci-hcd
[    2.407603] usb usb4: SerialNumber: xhci-hcd.9.auto
[    2.409479] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.409661] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[    2.409672] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.409680] usb usb5: Product: xHCI Host Controller
[    2.409688] usb usb5: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 xhci-hcd
[    2.409696] usb usb5: SerialNumber: xhci-hcd.9.auto
[    2.412820] usbcore: registered new interface driver iforce
[    2.412930] usbcore: registered new interface driver xpad
[    2.413499] usbcore: registered new interface driver usbtouchscreen
[    2.460412] usbcore: registered new interface driver uvcvideo
[    2.467045] usbcore: registered new interface driver bfusb
[    2.467181] usbcore: registered new interface driver btusb
[    2.519667] of_get_named_gpiod_flags: parsed 'gpios' property of node '/switches/usb-switch[0]' - status (0)
[    2.520720] usbcore: registered new interface driver usbhid
[    2.520723] usbhid: USB HID core driver
[    2.523452] usbcore: registered new interface driver snd-usb-audio
[   13.435160] usb 5-1: device not accepting address 2, error -62
[   24.283144] usb 5-1: device not accepting address 3, error -62
[   24.320263] usb usb5-port1: attempt power cycle
[   25.360147] usb usb5-port1: cannot disable (err = -32)
[   25.394161] usb usb5-port1: cannot disable (err = -32)
[  889.555166] usb 5-1: device not accepting address 5, error -62
[  900.419178] usb 5-1: device not accepting address 6, error -62
[  900.464160] usb usb5-port1: attempt power cycle
[  901.502224] usb usb5-port1: cannot disable (err = -32)
[  901.549246] usb usb5-port1: cannot disable (err = -32)


  Hardware Status Monitoring?
Posted by: Leapo - 03-20-2018, 12:48 PM - Forum: Linux on Rock64 - Replies (7)

Is it possible to measure hardware status (core temperature, core voltage, core clock, memory voltage, memory clock, etc.) on the Rock64 under Linux? So far, I've managed to read core temperature and clockspeed, but that's about it.

I know vcgencmd works on the Raspberry Pi, and was ported to the Pine64, but I haven't seen anything similar for the Rock64.


  android locked!!
Posted by: kyllo - 03-20-2018, 10:22 AM - Forum: Android on Rock64 - Replies (4)

I installed in my rock64 android emmc following this tutorial http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf and all good, but when it starts in a few seconds, it gets stuck.

You know that you can be? Thank you.


  Monitor Display Resolution
Posted by: Riverman - 03-19-2018, 04:10 PM - Forum: Android on Rock64 - Replies (2)

HDMI to standard computer monitor. 
The monitor native resolution is 1680x1050. 
Settings->Display selection is HDMI. 
Resolution list shows 1680x1050 as an option but if I click 1680X1050p-60 the screen goes black then comes back with no change. 
Always defaults to 1280x720p-60.


Monitor ViewSonic VA2226w
Native Resolution 1680 x 1050 at 60 Hz

Tried 

Android 7.1.2 Stock Image [microSD Boot] [Rooted] [20171204]
Android TV 7.1 Community Build Image [microSD Boot] by ayufan


  Android touchscreen capabilities?
Posted by: horacejlee - 03-19-2018, 08:56 AM - Forum: Android on Pine A64(+) - Replies (6)

Hi all,
I'm thinking of buying a Pine A64 along with the 7" touch screen panel, can you let me know whether Android supports touch gestures like scrolling and zooming, and does it include a virtual keyboard like on a regular Android phone/tablet?
Thanks.


  CPU clocks
Posted by: Arkadiusz - 03-19-2018, 03:05 AM - Forum: General Discussion on ROCKPRO64 - Replies (6)

Hi,

I can not find any information regarding SoC freq used.
How it compare to Rock64, which uses 1296 MHz clock?


BR

Arek


  weird errors on boot
Posted by: Mentaluproar - 03-18-2018, 08:39 PM - Forum: Linux on Rock64 - Replies (9)

When I tried flashing the latest release OpenMediaVault 64bit image to emmc, I got a never ending stream of sector errors.  It stopped when I put in an sd card and tried booting again.  Later, I connected my external hard drives and UPS.  The thing kept redecting all USB devices over and over, and never completing a boot.

I tried booting off microSD withthe Sd to eMMC image, and the first time, it loaded and couldn't complete the dd.  I rebooted and did it again, without disconnecting power and this time it worked, but rebooted to the above issues again.

Is the rock64 board still not ready for prime time yet? Do I have a bad eMMC? What is the average airspeed velocity of an unladen swallow?


  slarm64 (unofficial slackware) Rock64 RK3328 (aarch64)
Posted by: mara - 03-18-2018, 11:50 AM - Forum: Linux on Rock64 - Replies (133)

support for slarm64 for rock64 development boards (aarch64 unofficial port slackware)
the system can be assembled as armhf and aarch64, assemblies are made under aarch64


links:

         site: fail.pp.ua
         forum: linuxquestions
         development: https://gitlab.com/sndwvs/images_build_kit

shortly about the slarm64, a simple non-overloaded system for everyday and not just use.