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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 28,132
» Latest member: farareaa
» Forum threads: 15,690
» Forum posts: 114,585

Full Statistics

Latest Threads
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: zetabeta
3 hours ago
» Replies: 23
» Views: 2,292
Using Signal on PinePhone...
Forum: PinePhone Software
Last Post: dragonhospital
4 hours ago
» Replies: 47
» Views: 13,574
More powerful smartwatch?
Forum: Getting Started
Last Post: Pavlos1
6 hours ago
» Replies: 1
» Views: 43
Firmware Update for PineP...
Forum: General
Last Post: Pavlos1
6 hours ago
» Replies: 1
» Views: 44
Writing to SD card possib...
Forum: PinePhone Software
Last Post: Fadazo
Yesterday, 04:01 PM
» Replies: 6
» Views: 3,341
Firefox does not work on ...
Forum: PostmarketOS on PinePhone
Last Post: Haddoud
Yesterday, 03:14 PM
» Replies: 1
» Views: 55
How to do automatic login...
Forum: Mobian on PinePhone
Last Post: Haddoud
Yesterday, 02:50 PM
» Replies: 1
» Views: 1,015
Armbian and LibreELEC and...
Forum: Linux on Quartz64
Last Post: balbes150
Yesterday, 09:09 AM
» Replies: 148
» Views: 59,886
Progress on Wifi Chip
Forum: PineTab Hardware
Last Post: frtodd
05-01-2024, 10:25 AM
» Replies: 0
» Views: 74
PinePhone Pro EDL boot by...
Forum: PinePhone Pro Hardware
Last Post: traut
05-01-2024, 09:29 AM
» Replies: 1
» Views: 49

 
  Not able to write u-boot to SPI
Posted by: Jix0 - 10-29-2018, 11:08 AM - Forum: General Discussion on ROCKPRO64 - Replies (2)

Hello everyone.

I have a trouble flashing uboot to my RockPro64 4GB variant. I am trying to use rock64_write_spi_flash.sh script, but nothing is flashing.

I made all steps according to wiki, booted from SD card, used latest ubuntu image, but everything I get is following error:


Code:
rock64@rockpro64:/dev$ sudo su
[sudo] password for rock64:
root@rockpro64:/dev# rock64_write_spi_flash.sh
Doing this will overwrite data stored on SPI Flash
 and it will require that you use eMMC or SD
 as your boot device.

Type YES to continue or Ctrl-C to abort.
YES
Writing /dev/mtd0 with content of /usr/lib/u-boot-rockpro64/rkspi_loader.img
Erasing 4 Kibyte @ 0 --  0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 0 (mtd0)
       error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
            error 110 (Connection timed out)
Erasing 4 Kibyte @ 1000 --  0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 1 (mtd0)
       error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
            error 110 (Connection timed out)
Erasing 4 Kibyte @ 2000 --  0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 2 (mtd0)
       error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
            error 110 (Connection timed out)
Erasing 4 Kibyte @ 3000 --  0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 3 (mtd0)
       error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
            error 110 (Connection timed out)
Erasing 4 Kibyte @ 4000 --  0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 4 (mtd0)
       error 110 (Connection timed out)
flash_erase: error!: /dev/mtd0: MTD Erase failure
            error 110 (Connection timed out)
Erasing 4 Kibyte @ 5000 --  0 % complete ^C^C


I have even tried steps written here: https://forum.pine64.org/showthread.php?...e#pid40677   (,only changed the overlay address to "ff1d0000" to fit to RockPro64 dts).

I never flashed anything to SPI before, so it can't be messed up. I tried the SD card method with only ayufan uboot image and this don't work either. Nothing is written to it..

Output of "mtdinfo":

Code:
root@rockpro64:/dev# mtdinfo
Count of MTD devices:           3
Present MTD devices:            mtd0, mtd1, mtd2
Sysfs interface supported:      yes

root@rockpro64:/dev# mtdinfo /dev/mtd0
mtd0
Name:                           loader
Type:                           nor
Eraseblock size:                4096 bytes, 4.0 KiB
Amount of eraseblocks:          1016 (4161536 bytes, 4.0 MiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:0
Bad blocks are allowed:         false
Device is writable:             true

root@rockpro64:/dev# mtdinfo /dev/mtd1
mtd1
Name:                           env
Type:                           nor
Eraseblock size:                4096 bytes, 4.0 KiB
Amount of eraseblocks:          8 (32768 bytes, 32.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:2
Bad blocks are allowed:         false
Device is writable:             true

root@rockpro64:/dev# mtdinfo /dev/mtd2
mtd2
Name:                           vendor
Type:                           nor
Eraseblock size:                4096 bytes, 4.0 KiB
Amount of eraseblocks:          64 (262144 bytes, 256.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:4
Bad blocks are allowed:         false
Device is writable:             true


Output of dmesg:
Code:
root@rockpro64:/dev# dmesg | grep spi
[    2.015555] rockchip-spi ff1d0000.spi: Failed to request TX DMA channel
[    2.016160] rockchip-spi ff1d0000.spi: Failed to request RX DMA channel
[    2.016778] rockchip-spi ff1d0000.spi: no high_speed pinctrl state
[    2.017904] m25p80 spi32766.0: gd25q128 (16384 Kbytes)
[    2.018394] 3 ofpart partitions found on MTD device spi32766.0
[    2.018924] Creating 3 MTD partitions on "spi32766.0":
[  164.537097] m25p80 spi32766.0: flash operation timed out
[  204.537255] m25p80 spi32766.0: flash operation timed out
[  244.537347] m25p80 spi32766.0: flash operation timed out
[  284.537402] m25p80 spi32766.0: flash operation timed out
[  324.537509] m25p80 spi32766.0: flash operation timed out
[  364.537587] m25p80 spi32766.0: flash operation timed out


Thanks for any suggestions. This is really driving me nuts.. Any help will be appreciated.. :-)


  Centos 7 on rock64
Posted by: smnoufal - 10-29-2018, 04:23 AM - Forum: Linux on Pine A64(+) - Replies (6)

I want to run Centos 7 on rock64 rk3328 chipset. Any sort of help is appreciated.

Regards,


  How to change DSI Clock
Posted by: r.tanaka - 10-29-2018, 04:03 AM - Forum: LCD and Touch Panel - No Replies

Hi everyone

How do I change the DSI clock?

The software and hardware used are as follows.

Hardware: PINE A64-LTS
Software: Armbian

Thank you.


Star New Pinebook releases (28.10.2018) - Ayufan
Posted by: Luke - 10-29-2018, 03:34 AM - Forum: Linux on Pinebook - Replies (5)

New Pinebook releases from ayufan - including Bionic with LXDE, Xenial with Mate and Stretch minimal.

Do note that that OS images designated for Pinebooks with 1080p IPS panel are designated accordingly. N.B. The new images are also available for Pinebooks from previous batches with non-1080p ISP screens.

Download here


  WIFI driver compilation
Posted by: wsk - 10-28-2018, 04:34 AM - Forum: Rock64 Hardware and Accessories - Replies (1)

Hello everyone,

I have a Rock64 board and have two USB wifi adapters, one with rtl8192SU chip and the other with rtl8192EU. I have spent several days trying to compile the drivers for both and changed the system from debian to ubunto and back. I cannot get the system to compile the drivers. I followed the threads here and the readme on github for several versions. Nothing is working. Can anyone direct me to a tutorial about the preparation of the system for compiling the drivers that would be enough to get this to work? I now have armbian. I successfully installed the .deb driver but it cannot identify the hardware and the driver does not show in the sysotem.

Any help is appriciated.


  Plexdrive on RockPro64
Posted by: carracedo - 10-27-2018, 04:43 PM - Forum: General Discussion on ROCKPRO64 - No Replies

Can someone help me install plexdrive in RockPro64.

I'm trying it with DietPi but so far I have not succeeded.

Thank you so much guys.


  Smooth playback of 4K videos working under Ubuntu / mpv
Posted by: danboid - 10-27-2018, 01:15 PM - Forum: General Discussion on ROCK64 - Replies (2)

One of the main reasons I bought my rock64 was in the hope of being able to use it to play 4K videos. Although I have achieved that previously with libreelec, libreelec/kodi would always crash or reboot on me after a while plus I'd prefer to run a regular/proper Linux distro and mpv is a much more powerful video player than kodi is.

Today I finally got 4K videos to play back smoothly using mpv under ayufan's bionic/lxde Ubuntu image. The secret, as disclosed by @fcoulombe on github, was to edit /usr/local/bin/rkmpv and add:


 --drm-mode=21

To the mpv options, which fixed the green lines and very jerky playback I was experiencing without. A lot of my videos require that I also use the switch

 --video-aspect=1.3333 (and --video-rotate=no)

as using that rids of the letterboxing.

https://github.com/ayufan-rock64/linux-build/issues/249


  Odd HDMI issues
Posted by: jman005 - 10-26-2018, 09:15 PM - Forum: General Discussion on ROCK64 - No Replies

Hey there,
I've been trying to set up the rock64 with an HDMI LCD (this one) for a while now. HDMI output works fine with regular monitors - however, when I try to connect to the LCD oddities follow. When using Ubuntu Mate, the LCD briefly flashes on (to a black screen) and off. I was told this may be an issue with resolution size, so I tried to use another monitor to change it; however, connecting to the LCD seemed to have broken the HDMI output. I re-flashed the MicroSD with an LXDE distro which seemed to fix the issue, then decreased the resolution before connecting to the LCD, but the same results occurred with the only difference being that the LCD displayed a 'no signal' message rather than flashing on and off.

Any suggestions? Thanks in advance.


  Anybody used lirc?
Posted by: ab1jx - 10-26-2018, 08:38 PM - Forum: Linux on Rock64 - Replies (1)

I haven't successfully, frankly.  I've had IR on a couple of laptops before but gave up.  What I want it for is that I think I should be able to back up my IR remotes like for TVs.  When they die, and I've seen a few do that, I'll have the codes I need to program a universal remote.  I think lirc will give me an ASCII value for each key on the remote that I press, I just need to take careful notes of what button gives what code.

I did a quick search for infrared on this board and the only thing it turned up was something about the IR sensor not being connected until you. plug a jumper in or something like that.  Except I'm not getting far enough to scan for devices.  By its man page lirc-setup should:

Quote:       A  simple  GUI  tool which creates a lirc configuration after some user
       dialogs which  defines  driver,  device,  modprobe  actions,  etc.  The
       results  are  written  as  separate files in the output directory which
       defaults to lirc-setup.conf.d

Here's what I see:

Code:
apt-get install lirc
---------
rock64# lirc-setup
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Traceback (most recent call last):
 File "/usr/bin/lirc-setup", line 10, in <module>
   import mvc_control
 File "/usr/lib/aarch64-linux-gnu/python3/dist-packages/lirc/mvc_control.py", line 15, in <module>
   import mvc_model
 File "/usr/lib/aarch64-linux-gnu/python3/dist-packages/lirc/mvc_model.py", line 13, in <module>
   import yaml
ImportError: No module named 'yaml'

----------------

rock64# dpkg-query -l | grep yaml
ii  libyaml-0-2:arm64                                      0.1.7-2                           arm64        Fast YAML 1.1 parser and emitter library
ii  python-yaml                                            3.12-1                            arm64        YAML parser and emitter for Python

------------
ps ax | grep lirc
8719 ?        Ss     0:00 /usr/sbin/lircd --nodaemon
8754 ?        Ss     0:00 /usr/sbin/lircmd --nodaemon
8774 ?        Ss     0:00 /usr/bin/irexec /etc/lirc/irexec.lircrc
8789 ?        Ss     0:00 /usr/sbin/lircd-uinput
9008 pts/0    S+     0:00 grep lirc

I think the import error comes from something Python.  "pip install yaml" didn't get me anywhere.  lirc goes back at least 10 years, maybe it's not maintained anymore.  By the ps ax lircd is running.  So it's maybe-broken hardware and newbie user who should have RTFMed better.

pip install mvc_control and mvc_model both get "not found" errors.

Code:
rock64# apropos lirc
irdb-get (1)         - list, search and download lirc configuration files.
irpipe (1)           - tool to send data to lircd over /dev/irpipe kernel dev...
irrecord (1)         - IR-codes recording tool for usage with LIRC
irsend (1)           - basic LIRC program to send infra-red commands
lirc-config-tool (1) - tool to scan and generate lirc config files
lirc-lsplugins (1)   - Print dynamic modules info
lirc-lsremotes (1)   - parse lirc configuration files.
lirc-make-devinput (1) - create a devinput.lircd.conf for the local site.
lirc-setup (1)       - Interactive lirc setup tool
lircd (8)            - Decode infrared signals and provide them on a socket.
lircd-setup (8)      - Run setup commands in lirc_options.conf
lircd-uinput (8)     - Forward lirc button presses as uinput events
lircd.conf (5)       - lirc main configuration file
lircmd (8)           - Translate infrared signals into mouse events.
lircrc (5)           - application-specific remotes signals configuration
lircrcd (8)          - Synchronize lircrc state among client applications.
pronto2lirc (1)      - convert pronto-encoded data to lircd.conf format
rock64#
Juicy tidbits


  problems with emmc adaptor imaging
Posted by: insanescouter - 10-26-2018, 06:35 PM - Forum: Android on Rock64 - No Replies

Not sure what I am doing wrong. I was able to get the android 7.1 sd to emmc to work no problem. But using 2 different usb emmc adaptors (the pine64 one, and one I got off amazon) and have tried many different images and none of them will boot for me. Its like I am missing a step or something.

I am running ubuntu on my laptop, and using the pine64 etcher clone to do the imaging. I have tried downloading images to my drive and i have tried letting it download them for me. No luck.

Official etcher mostly complains that none of the images have a boot partition, yet im downloading the xz ones. I have also tried ayufan-rock64's android-7.1-rock-64-rock64_regular-v0.3.12-r114-raw.img.gz as I really want a normal android install, not the tv version but still no luck.

No matter what I have tried it sits there for days showing me "android" on the screen or it goes in constant reboot cycles, or just does nothing.

By the way I also have an older pine64 a64 without the emmc slot and I have had no issue doing the sd images for it and like bliss os for it.

Ive read the instructions at http://wiki.pine64.org/index.php/NOOB under "Flashing Using the USB-to-eMMC Adaptor (Preferred Way)" and for life of me cant figure out why its not working.

Thanks for any help... ive been at this for like a month and getting nowhere, could the emmc chip that I got from pine64 be faulty?