Hi,

It is 21st century. Please make the forum and other pages be run over secure HTTPS. It is easy to intercept passwords and email addresses quiet easily otherwise by hostile parties or run untrusted javascript and change user links to various binaries and iso images to point to various malware binaries, etc.

Thanks.

I have an xprotolab plain o-scope.  The software for it is written in QT, which means that, in theory, I should be able to get it running on the Pine64.

My only problem is that I have QT4 by default, and need QT5.

How do I go about installing QT5 and telling the system to use QT5 instead of QT4?  I've searched online, and all it's done is confuse me.

Once QT5 is installed, I think it's just a matter of running cmake to make the software.

Thanks in advance!
RIck

Is this possible? Trying to use a 21:9 monitor (2560x1080p60). The only resolution open is standard 1080p resolution.

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

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.

I think that my LCD Touch Panel is defective (I hope I'm wrong). 

First of all I've to say that I owe 2 Micro SD cards. The first one has the "Lollipop Beta 2 (LCD Version)", and the second one has the "Lollipop Beta 2 (HDMI Version)" both downloaded from the website.

Here is an image that shows how my LCD Touch Panel is connected to the board. (My mobile camera is ashame).



As you can see it's all correctly connected with all the pins down... The thing is that I've tried both HDMI Img (on my living room TV) and LCD Img on my LCD Touch Panel. Here i'll show u the results.

HDMI (living room TV):



LCD Touch Panel:




As you can see the image works in both screens, but the LCD one can barely be read. I can assure you that i got to the "desktop" on both applications and that the Touch Panel works (I know it isn't connected in the posted screens, but I did test it before), but I don't get why it emits that low brightness (I've turned the Android brightness to max already and it's not that).

I would appreciate any advice, cause I don't know if I am doing anything wrong.

Hi all!

Pine64 is a very cost effective solution for running the UniFi Controller. The installation process is a bit tricky though. Hence sharing my experience: https://ishwestscriptwault.wordpress.com...pine64-en/

Enjoy!

Check out the drop of the H5SDK Orange Pi posted.

https://github.com/orangepi-xunlong/Oran...4/boot/dts

Aren't these w1p1 files the A64 and the w2p1 stuff the H5?

sun50iw1p1-clk.dtsi
sun50iw1p1-fpga.dts
sun50iw1p1-perf1_v1_0.dts
sun50iw1p1-perf2_v1_0.dts
sun50iw1p1-perf3_v1_0.dts
sun50iw1p1-pinctrl.dtsi
sun50iw1p1-soc.dts
sun50iw1p1-t1.dts
sun50iw1p1.dtsi

It is truly idiotic that everyone outside of China has to rely on Allwinner to release the code to their Chinese OEMs and then those OEMs turn around and post it for everyone to see. Why can't they just put this stuff on a public server like everyone else does?

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 (2DR2,3DR3,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.

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...