Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
fixing the ppkb mainboard...
Forum: PinePhone Pro Accessories
Last Post: zetabeta
Today, 12:04 AM
» Replies: 1
» Views: 47
|
Pinephone pro stuck while...
Forum: PinePhone Pro Hardware
Last Post: Supervisor
Yesterday, 06:40 PM
» Replies: 2
» Views: 81
|
Compatible U.S. carriers ...
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
08-15-2025, 07:34 PM
» Replies: 2
» Views: 115
|
Long dialpad keypress to ...
Forum: Mobian on PinePhone
Last Post: Zebulon Walton
08-15-2025, 06:48 PM
» Replies: 3
» Views: 91
|
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: Kevin Kofler
08-15-2025, 06:20 PM
» Replies: 4
» Views: 890
|
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: zetabeta
08-15-2025, 12:27 PM
» Replies: 6
» Views: 343
|
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: zetabeta
08-15-2025, 04:22 AM
» Replies: 3
» Views: 156
|
prototyping to help someo...
Forum: General
Last Post: xerosenex
08-14-2025, 02:31 AM
» Replies: 0
» Views: 101
|
Password reset via u-boot...
Forum: PineNote Software
Last Post: lunnabae
08-13-2025, 01:17 AM
» Replies: 6
» Views: 1,753
|
incorporate a multimeter ...
Forum: General
Last Post: lalisa12
08-13-2025, 01:14 AM
» Replies: 2
» Views: 523
|
|
|
My Pinebook have been arrived, but cannot be charged |
Posted by: mtmicrosystems - 10-14-2017, 06:27 PM - Forum: General Discussion on Pinebook
- Replies (8)
|
 |
Dear,
My Pinebook have been arrived, but cannot be charged.
Whenever I plug the A/C adapter, it doesn't work, and my Pinebook battery is decreased again and again.
The main reason is , I use it in China, but I have requested an EU Standard AC Adapter,
Model : EE-0530-E
INPUT 100-240V ~ 50/60 Hz 0.5A
OUTPUT: 5v 3000mA
Can anybody help me , what else should I buy? Can anybody give a taobao.com link , in order that I can have a new A/C Adapter to charge my Pinebook battery?
Thank you.
Best Regards,
Gavin
|
|
|
unreliable serial console output?! |
Posted by: consoleadam - 10-14-2017, 06:43 AM - Forum: General Discussion on ROCK64
- Replies (7)
|
 |
Together with Rock64/1GB board, I have bought the USB serial console as listed on Pine/Rock64 site. Booting the board with the community build of 'xenial-i3-rock64-0.5.10-118-arm64.img'. On a linux workstation, using minicom (1500000 8N1 | NOR | Minicom 2.7 | VT102 | Offline | ttyUSB0), I can interact with the board check the following excerpts:
root@rock64:~# uname -a
Linux rock64 4.4.77-rockchip-ayufan-118 #1 SMP Thu Sep 14 21:59:24 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
root@rock64:~#
The issue is: it is highly unstable meaning if I run the same following command:
root@rock64:~# cat /proc/cpuinfo
multiple times, gives different outputs for each run (as shown below)!! Is this a common problem? is it hardware or software related?
appreciated your help on this matter.
---------------------------------------------------------
root@rock64:~# cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture : 0xd03
CPU revision : 4
processor : 1
BogoMIPS : 48.00
F : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd0 asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41n : 4
processor : 3
BogoMIPS : 48.00
Features : fp asimd evcture: 8
CPU variant : 0x0
CPU part : 0xd03
root@rock64:~# cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU partoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 c
CPU part : 0xd03
CPU revision : 4
processor : 2
BogoMIPS :ementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU partres : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementePU revision : 4
Serial : b5f2b912efc3f49b
root@rock64:~#
|
|
|
hostname and IP missing on router |
Posted by: skipper - 10-14-2017, 03:29 AM - Forum: Linux on Rock64
- Replies (3)
|
 |
Running:
https://github.com/ayufan-rock64/linux-b...m64.img.xz
Controlling the rock64 via Putty - SSH
When first connecting:
apt update
apt upgrade
Then I change /etc/hostname and in /etc/hosts I add my fixed public IP with the hostname from /etc/hostname.
I then do:
apt remove --purge network-manager
make sure resolvconf is not installed
then:
rm /etc/resolv.conf
then make a new resolv.conf:
nano resolv.conf adding my 2 nameservers IP addresses and save.
then (I want to have complete control of the IP of the rock64 with no odd interference from other files/scripts that I don't know about):
systemctl disable dhcpcd
systemctl enable networking (in order to get back to the "oldfashioned way")
then:
nano /etc/network/interfaces.d/eth0 (I use only the wired rock64 LAN port)
I enter:
allow-hotplug eth0
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address XX.XX.XX.XX
netmask XXX.XXX.XXX.XXX
gateway XX.XX.XX.XX
The IP addr and mask are not on the same network as my local network.
It is created as a 2nd static IPv4 route on the router (fritzbox 7490) with 5 fixed IP addresses. I am not able to add the external IP and MAC as it is not on the same network as the fritzbox.
I then reboot the rock64.
When looking at the network connections tab in the fritzbox I don't see the rock64 (with it's new hostname and external IP) - tried several reboots of the rock64 and the router.
FYI when I do all this from a Rpi, Bpi, odroid or olimex I always see each of them on the fritzbox, with their hostname and external IP.
What can/could cause the missing fritzbox entry from the rock64?
It puzzles me and is annoying, as I need to create port permissions for the rock64 through the fritzbox from outside.
|
|
|
Confirmation of Order / Shipping |
Posted by: sleipneer - 10-12-2017, 11:42 PM - Forum: General Discussion on ROCK64
- Replies (3)
|
 |
Hey there,
i just wondered about the Communications.....
I ordered a Rock64 4GB with a bit of other stuff on Monday, 9th (#52700) and i get no informations about a shipping date oder something like that.
Can anybody tell me, whats the expected time for shipping to Germany?
Thanks in advance,
Ben
|
|
|
gpio driver porting from an r-pi3b |
Posted by: gene83 - 10-12-2017, 08:12 PM - Forum: Rock64 Hardware and Accessories
- Replies (9)
|
 |
I've an spi driver that runs on a pi3, writing (and reading from) 32 bit packets at nominally 42 megabaud, to a mesa 7i90HD cnc interfacing card, and reading back at 25 megabaud. But its full of code that checks to make sure its running on a pi. It also has an include file that describes the bcm2835 for all its offsets etc. I can excise the pi checks, but what else do I need to do to make it run on the rock64? The spi port used is nominally the SPI1 address in the pi scheme of things.
Thanks & Cheers
gene83
|
|
|
Receiving errors about eMMC (?) |
Posted by: acasta - 10-12-2017, 11:31 AM - Forum: General Discussion on ROCK64
- Replies (11)
|
 |
TL;DR: Ayufans latest eMMC-Mate-image. Strange errors in dmesg. See snippet below. Need help interpreting.
----------------
Hi! After some weeks of using my rock64 as bookshelf decoration, I'm finally starting to tinker with it.
At first, I hit some smaller bumps like using the official Mate image and loosing USB power after login.
Now I'm using ayufans latest eMMC Mate image. Installation to the eMMC module was super unproblematic. First reboot worked fine. Did some basic first login stuff (keyboard-layout, password, ...), and issued a reboot command. System tried to start, but delivered a black screen with a blinking cursor. I let it sit like this for about fifteen minutes ("just let it work. who knows, what's going on inside"), then I did a hard reset. System started to graphical login prompt. Typed in password, login box vanished, and that was it. Again fifteen minutes, this time only with the blue rock64 background.
I grew a bit concerned, but after another hard reset, the system bootet up and everything was fine. And since this last reset it's been stable and useful: No more freezes, quick boot and login, USB power and ethernet woking fine, all looking bright and shiny.
Then I made the error and issued the dmesg command. You know, just out of curiosity. Not that I could understand what it tells me. Just wanted to see what's going on.
And there I saw them: Errors. Colored brightly red, lots of errors about mmcblk0.
Small snippet of dmesg output:
Code: [ 23.781898] mmcblk0: retrying using single block read
[ 23.825835] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 23.991919] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[ 23.991933] mmcblk0: error -110 transferring data, sector 3279888, nr 256, cmd response 0x900, card status 0xb00
[ 23.992879] mmcblk0: retrying using single block read
[ 24.120340] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[ 24.120355] mmcblk0: retrying because a re-tune was needed
[ 24.321852] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[ 24.340830] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 24.506898] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[ 24.506914] mmcblk0: error -110 transferring data, sector 265240, nr 232, cmd response 0x900, card status 0xb00
[ 24.507855] mmcblk0: retrying using single block read
[ 24.577818] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 24.742932] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[ 24.742947] mmcblk0: error -110 transferring data, sector 10191680, nr 144, cmd response 0x900, card status 0xb00
[ 24.743909] mmcblk0: retrying using single block read
[ 24.835882] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 24.850620] tty_port_close_start: tty->count = 1 port count = 2.
[ 25.001946] mmcblk0: error -110 transferring data, sector 5610720, nr 32, cmd response 0x900, card status 0x0
[ 25.002839] mmcblk0: retrying using single block read
[ 25.306353] mmcblk0: retrying because a re-tune was needed
[ 25.599857] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[ 35.494818] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 35.660947] mmcblk0: error -110 transferring data, sector 8489664, nr 152, cmd response 0x900, card status 0x0
[ 35.661864] mmcblk0: retrying using single block read
[ 35.707819] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 35.873936] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[ 35.873950] mmcblk0: error -110 transferring data, sector 8486664, nr 224, cmd response 0x900, card status 0xb00
[ 35.874895] mmcblk0: retrying using single block read
[ 38.238823] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 38.404938] mmcblk0: error -110 transferring data, sector 3006264, nr 256, cmd response 0x900, card status 0x0
[ 38.405854] mmcblk0: retrying using single block read
[ 38.830921] mmcblk0: retrying because a re-tune was needed
[ 39.124857] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[ 39.864829] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[ 40.030909] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[ 40.030923] mmcblk0: error -110 transferring data, sector 5127832, nr 56, cmd response 0x900, card status 0xb00
[ 40.031846] mmcblk0: retrying using single block read
Seeing similar errors after reboot(s) made me really concerned. I tried my google-fu, but with limited success:
- Googling the "dwmmc [...] Unexpected command timeout [...]" line did not bring up any results.
- Googling the "error -115" line also did not yield useful hints (or I did not recognise them as such)
- Googling the "error -110" line was to some extent successful:
I stumbled across a NXP forum thread discussing a very similar error message. Their accepted answer was that the SD-card was "too fast". I don't know whether this is correct or not, but also their problem description is missing the "error -115". (And I am using the 32GB eMMC module, not an SD-card.)
Whilest playing around with the rock64 and dmesg, I made some further observations: - When idling, usually no further errors occur. When doing stuff (opening programs, ...), errors continue.
- The amount of errors is random. I even had one completly error-free boot.
- In dmesg-output, at ~305 sec runtime, I get three EXT4-fs entries, telling about number of errors since last fsck.
- Only the "-110" error is colored red, the "-115" is not. (Maybe less dangerous?)
To clarify: I have a tiny bit of linux experience, but really tiny. Someone showed me "dmesg", now all I know about errors and logging in Linux is dmesg. I also have a Raspberry Pi, and installed Owncloud on it (by following a tutorial). But that's really where my abilities end. To the most part I have no idea what's going on, it feels like stumbling around in the fog. But I am willing to learn about Linux and Rock64 (even though I really should invest my time in other things right now).
I would be very grateful, if someone could shed some light on these error issues.
-ac
_______
Side note to board administrators: I could not decide whether to put this thead under "Linux" or under "Hardware", so I ended up in "General Discussion" - just to be on the wrong side either way. Feel free to move this thread around. I am very new to forums (at least as active participant) and I am sorry.
|
|
|
|