Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
google will take control ...
Forum: General
Last Post: zetabeta
4 hours ago
» Replies: 22
» Views: 9,261
|
What's stopping you from ...
Forum: General Discussion of PinePhone Pro
Last Post: Jite
4 hours ago
» Replies: 3
» Views: 207
|
PINETAB-V doesn't boot.
Forum: Getting Started
Last Post: Woazboat
08-23-2025, 02:58 PM
» Replies: 1
» Views: 253
|
PinePhone Pro: Camera App...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-22-2025, 11:23 PM
» Replies: 3
» Views: 2,312
|
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-22-2025, 11:19 PM
» Replies: 9
» Views: 1,012
|
Booting Issues
Forum: PineNote Software
Last Post: serenopolveroso
08-22-2025, 11:36 AM
» Replies: 18
» Views: 5,021
|
Pinephone (Pro) Keyboard ...
Forum: PinePhone Accessories
Last Post: anernest
08-22-2025, 09:21 AM
» Replies: 1
» Views: 1,650
|
Multiple NEMA 17 stepper ...
Forum: General
Last Post: Harry
08-22-2025, 12:24 AM
» Replies: 0
» Views: 169
|
Giving away a Pinebook Pr...
Forum: Pinebook Hardware and Accessories
Last Post: tuxifan
08-21-2025, 03:11 AM
» Replies: 2
» Views: 284
|
Bare metal on Pinephone P...
Forum: PinePhone Pro Software
Last Post: alain
08-19-2025, 07:58 AM
» Replies: 0
» Views: 297
|
|
|
I found ADB debugging method via USB(OTG) Port |
Posted by: spbrain - 01-21-2018, 07:47 PM - Forum: Android on Pine A64(+)
- Replies (1)
|
 |
I really needed ADB debugging via USB(OTG). But it was hard to find the right solution.
At first I was frustrated because I did not have much information about this problem.
I have tried to solve this problem in the last few days.
Through the efforts of the past, we find one way to share.
First
Modify the USB settings in the sys_config.fex file.
The port PH09 is used as an OTG cellactor, but it does not seem to have much relation with the switcher.(Using S/W Switch)
[usbc0]
usbc0_used = 1
usb_port_type = 2
usb_detect_type = 1
usb_id_gpio = port:PH09<0><1><default><default>
usb_det_vbus_gpio = "axp_ctrl"
usb_drv_vbus_gpio = port:power3<1><0><default><0>
usb_host_init_state = 0
usb_regulator_io = "nocare"
usb_wakeup_suspend = 0
;--- USB Device
usb_luns = 3
usb_serial_unique = 1
usb_serial_number = "20080411"
rndis_wceis = 1
After setting as above, boot with new build.
A Type to A Type Prepare the USB cable and connect it to the upper port.
Then issue the following command after the su command:
cat /sys/devices/soc.0/usbc0.5/usb_device
Afterwards, you can see that MTP and ADB are connected.
To use it again as a HOST, issue the following command:
cat /sys/devices/soc.0/usbc0.5/usb_host
I tested it with Android 5.1. (PINE64 LTS Version)
I originally thought that mode conversion should be done automatically using PH09 port, but it did not.
If you have a better idea, you might as well share it.
|
|
|
Booting from USB |
Posted by: Luke - 01-21-2018, 03:52 PM - Forum: General Discussion on ROCK64
- No Replies
|
 |
There's been a couple of people asking about a 'how-to' for USB booting on the Rock64.
There are now two sets of instructions on how to do it, which you can find here and here.
[edit]The ones I wrote up on the wiki are more detailed for complete beginners while the ones on git are appropriate for those that know and understand the basics.
|
|
|
Nextcloud not working with external harddrive |
Posted by: floweih - 01-21-2018, 07:06 AM - Forum: General Discussion on ROCK64
- Replies (2)
|
 |
hope someone can help me
I am trying to install nextcloud on my rock64. As the data directory I tried to use an external harddrive.
But there is an error when I try to use external harddrives as nextcloud data directory. When i use the
sd card as nextcloud data directory there are no probs
What I tried:
Mounting the Harddrive with fstab: UUID=a61b3225-3af0-439b-be5b-c54898b9aa46 /media/4TB ext4 defaults 0 2
Which works for everything except nextcloud
As an alternative I tried pmount as described on the howto for rock64. But this also doesnt work.
As OS I use debian
As nextcloud version 12.04
Any tips for nextcloud?
Greetings
|
|
|
Reboot Issue with ROCK64 Linux version 4.4.77-rockchip-ayufan-141 |
Posted by: techyjtmb - 01-20-2018, 09:54 AM - Forum: General Discussion on ROCK64
- Replies (9)
|
 |
I have a ROCK64 4GB setup and when I reboot I have a lot of trouble getting the unit stable.
Here are the errors that display on the screen:
core: dev_pm_opp_get_voltage: Invalid parameters
mali-utgard ff300000.gpu: Failed to get voltage for frequency 163840000: -34
devfreq ff300000.gpu: Couldn't update frequency transition information.
And then it goes into kernel panic mode. I have to completely power down the unit,
remove the hdmi, ethernet, and keyboard cable, wait for 30 seconds and then it will boot.
I have tried a different power supply and plugging it in to a different power source.
I have 3 other similar ROCK64's working fine.
|
|
|
Unable to flash Android TV on eMMC: rkflashtool error |
Posted by: fbossi - 01-20-2018, 06:53 AM - Forum: General Discussion on ROCK64
- Replies (3)
|
 |
Hello everybody,
I'm trying to flash my 64GB eMMC with the latest Android TV build from ayufan: https://github.com/ayufan-rock64/android...3-r115.zip
I've been following this guide: http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf
I'm running Arch Linux. I also tried the exact same steps on a Ubuntu 17.10 machine and I got the exact same behaviour.
Here's the output of the rkinstall script:
Code: + rkflashtool P
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: writing flash memory at offset 0x00001c00... Done!
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w uboot
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: uboot
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w trust
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: trust
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w misc
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: misc
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w kernel
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: kernel
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w boot
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: boot
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w recovery
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: recovery
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w system
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: system
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ rkflashtool b
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: rebooting device...
Please note the "Error: 'mtdparts' not found in command line" lines.
This is the output of rkflashtool n:
Code: rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: Flash ID: 00 00 00 00 00
rkflashtool: info: Flash Info:
Manufacturer: Samsung (0)
Flash Size: 0MB
Block Size: 0KB
Page Size: 0KB
ECC Bits: 0
Access Time: 0
Flash CS:
I have tried to boot my ROCK64 and flash the image in all the following modes:
- Loader Mode, as suggested in ayufan's guide (hold Recovery, press Reset, release Recovery after 3 seconds) and also as suggested in the SADIE script (hold Reset, hold Recovery, release Reset, release Recovery after 3 seconds). Please note that I'm NOT actualy running the SADIE script.
- Normal boot (by simply pressing the Power button)
- MASKROM boot (by pressing the Power button after short-circuiting the eMMC PINS with a jumper)
(Acually I really have no idea how to verify which mode my ROCK64 is actually booting into... Does anybody know a way? Maybe using UART?)
Regardless of what mode I'm trying to use, I ALWAYS get the same ouput for all commands (including the MASK ROM MODE line!).
Unfortunately I do not have a eMMC -> USB adapter (after reading the guides I concluded that it was not strictly necessary anymore so I did not purchase it) so I'm stuck to flashing directly on the board.
So in the end I'm stuck right now. Any help would be really appreciated.
|
|
|
Where to buy replacement AC Adapter? |
Posted by: DazWilkin - 01-19-2018, 10:09 PM - Forum: General Discussion on Pinebook
- Replies (2)
|
 |
Folks --
A happy Pinebook (and 2x Pine64) user. I've broken the AC Adapter for the Pinebook and have been unable to find a replacement online.
Is anyone able to provide a link for me (US-based).
The model is EE-0530-E.
If not where I can buy a replacement, does anyone know the Pinebook's power plug dimensions?
Thanks!
|
|
|
Pinebook experiences |
Posted by: Bitflogger - 01-19-2018, 04:44 PM - Forum: General Discussion on Pinebook
- Replies (4)
|
 |
I dropped my Pinebook about 2.5 feet onto a carpeted floor. It hit on an edge. No apparent damage and it still works!
The space bar sometimes needs extra hitting to work. Where on the space bar I press seems to make a difference.
I use the command line "sudo apt-get ..." instead of the Software Updater, it says "not enough disk space on /boot".
When I try to press the backspace key, I somtimes accidentally press the power key. It then shuts down without a dialogue box.
It seems like a good buy for $99 plus $30 shipping. Its much better for general use than a pi book, which I also own.
|
|
|
|