Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,399
» Latest member: ejames82
» Forum threads: 16,169
» Forum posts: 116,775
Full Statistics
|
Latest Threads |
pinetab2 danctnix broken ...
Forum: PineTab Software
Last Post: acruhl
8 hours ago
» Replies: 2
» Views: 32
|
Zig booting up on PinePho...
Forum: General
Last Post: WhiteHexagon
Today, 03:11 AM
» Replies: 0
» Views: 19
|
3 questions, still no off...
Forum: PinePhone Pro Software
Last Post: jebez
Today, 01:53 AM
» Replies: 0
» Views: 36
|
New Install, apps start b...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
Yesterday, 07:56 PM
» Replies: 2
» Views: 30
|
What's a good image to us...
Forum: Linux on Pinebook Pro
Last Post: Dendrocalamus64
Yesterday, 07:28 PM
» Replies: 40
» Views: 9,391
|
US Mobile, via T-Mobile, ...
Forum: General Discussion on PinePhone
Last Post: dchang0
Yesterday, 04:24 PM
» Replies: 14
» Views: 10,687
|
many distros getting too ...
Forum: PinePhone Pro Software
Last Post: dchang0
Yesterday, 04:01 PM
» Replies: 3
» Views: 100
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
Yesterday, 02:16 PM
» Replies: 1
» Views: 67
|
Who remembers the Parall...
Forum: General
Last Post: paracpg
Yesterday, 02:41 AM
» Replies: 9
» Views: 10,039
|
touchscreeh doesn't accep...
Forum: PinePhone Pro Hardware
Last Post: henrythemouse
07-17-2025, 08:16 PM
» Replies: 9
» Views: 935
|
|
|
Custom boot animations |
Posted by: Bluphire - 12-30-2016, 11:18 AM - Forum: Android on Pine A64(+)
- Replies (4)
|
 |
Is it possible to change the boot animations in any of the currently released Android images? I used to change them on my phone's years ago after rooting, just wondering if it can be done on these builds.
Matt
|
|
|
BROM / Boot0 - Limitations |
Posted by: Flint - 12-30-2016, 08:42 AM - Forum: Pine A64 Hardware, Accessories and POT
- Replies (6)
|
 |
Hi guys, just received my Pines here some days ago (3 Pine64+ 2Gb models) and just started to play with.
I can load a Longsleep linux, and even some hand crafted 64Bits uboot with EFI from mainline, however, I've several questions regarding low-level and hardware related code.
From what I read here and there, at the initialization, the BROM is calling the boot0 binary which seems to be a closed source SPL program.
Could you explain me which limitations do you see about this unsourced boot0 SPL?
I'm thinking about reversing it but it would be something a little bit time consuming so I would love to have examples of really usefull features that could be implemented (on U-Boot/Linux for examples) without these limitations.
|
|
|
Christmas pine64 2GB - DOA |
Posted by: sendonline@yahoo.com - 12-28-2016, 07:02 PM - Forum: Getting Started
- No Replies
|
 |
Greetings all,
My brother gave me a pine64+ 2GB model for Christmas and I believe it's DOA.
Let me first start off that my power supplies certainly meet the requirements of this board with 2amp, 2.5 amp, and yes, I borrowed a 4.0 amp from my ws2812 strings to try. The voltages are tight to usb 5v specs.
I'm a long time user of Pi boards. All of the aforementioned power supplies work fine with my Raspberry Pis and so do the sdcards I've tried with the Pine.
I'm also a long time user of linux and consider myself advanced in the OS. I use "dd" to dump and read often for other systems. Every image I've dumped for the pine is fine. Some of the images I've tried create a fat for /boot, others have /boot in rootfs.
I tried several images and never got a thing, until I decided to hook up the debug port to a ttl adapter and this is what I got:
12/27/16-07:12:48 - HELLO! BOOT0 is starting!
12/27/16-07:12:48 - boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f
12/27/16-07:12:48 -
12/27/16-07:12:48 - boot0 version : 4.0.0
12/27/16-07:12:48 - set pll start
12/27/16-07:12:48 - set pll end
12/27/16-07:12:48 - rtc[0] value = 0x00000000
12/27/16-07:12:48 - rtc[1] value = 0x00000000
12/27/16-07:12:48 - rtc[2] value = 0x00000000
12/27/16-07:12:48 - rtc[3] value = 0x00000000
12/27/16-07:12:48 - rtc[4] value = 0x00000000
12/27/16-07:12:48 - rtc[5] value = 0x00000000
12/27/16-07:12:48 - DRAM driver version: V1.1
12/27/16-07:12:48 - rsb_send_initseq: rsb clk 400Khz -> 3Mhz
12/27/16-07:12:48 - PMU: AXP81X
12/27/16-07:12:48 - ddr voltage = 1500 mv
12/27/16-07:12:48 - DRAM Type = 3 (2 DR2,3 DR3,6:LPDDR2,7:LPDDR3)
12/27/16-07:12:48 - DRAM clk = 672 MHz
12/27/16-07:12:48 - DRAM zq value: 003b3bbb
12/27/16-07:12:48 - DRAM single rank full DQ OK
12/27/16-07:12:48 - DRAM size = 2048 MB
12/27/16-07:12:48 - DRAM simple test FAIL.
12/27/16-07:12:48 - initializing SDRAM Fail.
It appears the RAM is bad and never attempts to access the card which explains why none of the imaging I've done ever worked.
I submitted a ticket to them (overdue), but at this point I don't think I'll get a response. I sure hope they can do something. My brother, who doesn't have money waist and is disappointed as well.
This is my experienced thus far.
|
|
|
Node.js is not installed properly on Pine64 |
Posted by: nsisodiya - 12-28-2016, 02:07 PM - Forum: Ubuntu
- Replies (1)
|
 |
I installed node.js on ubuntu image using nvm.
nvm is very cool and best way to install node.js.
I guess, something is missing in kernel provided by longsleep...
Code: ubuntu@pine64:~$ file $(which node)
/home/ubuntu/.nvm/versions/node/v7.3.0/bin/node: ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=3d0c1229bb16cd420c34649d3763ec5e2d1fe03b, not stripped
ubuntu@pine64:~$ ldd $(which node)
linux-vdso.so.1 => (0x0000007fb0212000)
libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000007fb01f9000)
libstdc++.so.6 => /usr/lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000007fb006a000)
libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000007faffbe000)
libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000007faff9d000)
libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000007faff71000)
libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000007fafe2a000)
/lib/ld-linux-aarch64.so.1 (0x000000557faf8000)
ubuntu@pine64:~$ sudo apt-cache search linux-vdso
ubuntu@pine64:~$ sudo apt-cache search aarch64
qemu-system-arm - QEMU full system emulation binaries (arm)
qemu-system-aarch64 - QEMU full system emulation binaries (aarch64)
|
|
|
Facing difficulty in getting started with Ubuntu image |
Posted by: nsisodiya - 12-27-2016, 10:40 PM - Forum: Ubuntu
- Replies (4)
|
 |
1. I downloaded longsleep image (xenial-pine64-bspkernel-20161218-1.img.xz) !
I burned image and booted too.
I do not have any monitor with me. I do not have any keyboard with me. (actually i do not want to use it.)
How, can i do it. I used different hardware, where device was connected to Laptop. When C.H.I.P. was connected to laptop, using usb cable, I do not need cable. I just need to use screen utility to login on any tty
I connected a monitor and keyboard to what is available.. after login, I tried, ifconfig. ifconfig do not show any wlan0. I have connected my wifi module to Pine64. so, ideally it should show wlan0 too. unable to find instruction on how to connect wifi.
the worst thing, I tried to connect with LAN cable. router is very far from Work table. If I connect LAN cable, I cannot connect keyboard. So I thought , I can do ssh and let Pine64 to be connected on LAN cable without any keyboard.
When I connected with a LAN cable, It do not get any ip address. It should get ip address automatically, so that I can do a ssh.
I am highly frustrated, I cannot get stated on this board.
|
|
|
Official Android Release |
Posted by: MCZ - 12-27-2016, 08:05 AM - Forum: Android on Pine A64(+)
- No Replies
|
 |
Hi,
tl;dr
Is there an official Android Release with "release-keys" ?
I'm trying to run a VOD service I have in my country,
the thing is they are very strict with demands
(Only smartphones/tablets allowed)
I know a few people who managed to run the App using their Android Boxes
using root > changing "test-keys" to "release-keys" then using "hide my root"
and finally changing the identity of the Box to Android smartphone (Nexus or Samsung for example)
so, I don't want to go through all of that if there is already an official "release-keys" android OS here,
Thanks for reading,
MCZ
|
|
|
|