I was not expecting it to happen but the first time I opened the DSI header the locking part popped off.  I've used many of these connectors but non as flimsy is this.  Anyone else had the same experience?

It also seems to me that it's backwards, meaning I'd expect to insert the fpc/lcd on the outside of the board.  It's hard with such a tiny connector and your flex cable is getting bent by the Ethernet port.

I brought an pack of 10 replacements from amazon.  I'll have to be in the right mood to attempt removal and install of the header.

Attached Files

Thumbnail(s)
   

I've used the xenial-pine64-bspkernel-20160716-1.img to install the longsleep Ubuntu then did the apt-get update and upgrade.  

EDIT: I just reformatted my card, put on the brand new xenial-pine64-bspkernel-20161217-1.img, did all the other resize, etc, and got the same results below. I' replacing the output from yesterday with the output from today.
I'm trying to install XML-RPC via 
svn co -q https://svn.code.sf.net/p/xmlrpc-c/code/stable /tmp/xmlrpc-c
but when I get to the line:  ./configure
it fails because it is unable to guess the build type.
Has anyone been able to get this to work?  How would I go about checking the URLs in their comment to see if it would recognize this custom build? or how would I specify a build?  
I know this might be more of an XML-RPC support issue, but this has worked fine on other stock Ubuntu builds I've done in the past.
Thanks for any support you can offer.

http://www.banana-pi.org/m64-download.html
there are 2 android images working smooth

this link has working Android, Kano,Raspbian, Ubuntu windows IOT with all hardware supported.
http://www.banana-pi.org/m64-download.html

So while on the internet, I stumbled upon an Image of Raspbian for the pine64, it is technically for the banana pi64, but hardware is identical.

 It just so happens this is probably the easiest initial start for anyone new to pine64. First download the link here:
 https://drive.google.com/file/d/0B_YnvHg...sp=sharing

Unzip the folder to get the .img file, and burn the Image to a minimum 8Gb class4 sd card. Once you have got the sd card ready to boot, plug in your hardware you want to use, and boot. HDMI wont boot up instantly, so the first boot really just decompresses .img to its folders and files.

 Shutdown your pine64, put sd card into your windows or mac, or Linux to read the disk, you are looking for Config.txt open this file. Remove the #'s for the commands you want, such as HDMI, save file, eject.

 Now put the sd card back into your pine and boot, you will have linux penguins for a moment, then you will boot into the desktop with USB, Ethernet, HDMI all working. Now you can do raspberry pi projects with your pine64.

I'm looking at using some 3.3V peripherals that might need more amps than the Pine can deliver.  

Firstly, how much juice can the 3.3V pins source when powered by the on-board regulator?  (I'm assuming the various +3.3V pins on the Euler/Exp/PI bus are all connected and thus can source the same amount within their aggregate limit, or are their different limits for different 3.3V pins)

Secondly, if I need more +3.3V juice than the board can source, can I simply provide it via one of the 3.3V pins?  If I do this, can I disable the on-board 5V-->3.3V regulator some how?  (I want to avoid any chances of a voltage difference between the two 3.3V rails leading to one source sourcing into the other.)

Ideally, I'd like to use my own external PSU for supplying both 5V and 3.3V, and eliminating any hardware limitations of the boards on-board.

What do I need to do if I want to provide both +5V and +3.3V DC in?

This link to this image has been tested by me, I can verify HDMI Ethernet, Wifi, and USB after configuring the text file on windows then rebooted to a fully supported A64 Raspbian Image
 https://drive.google.com/file/d/0B_YnvHg...BFSnM/view
this works unexpectedly well.

I'm new to this so please don't be too hard on me.

I'm setting up an ADS1115 and I have it connected. (nothing being measured yet)

On the pine, I when I run
sudo i2cdetect -y 1
I can see that the ADS1115 is showing up at spot 48

sudo i2cdetect -y 0
shows nothing connected, all "--"

These are my two separate busses, right?

I try to run the sample script
sudo simpletest.py
sample code that is part of the github example for the ADS1115 and it returns a runtime error -
"Could not determine default I2C bus for platform"

I'm lost at what to do to fix it.
I've tried changing the python script to look specifically at address=0x48 on busnum=1, but I get the same error.

On another note, I tried adding i2c-dev to /etc/modules so that it will load and I don't have root access and cannot determine the password - does anyone know what the root password is for debian mate on the pine from longsleep? i've tried debian, password, root and all sorts of things but can't get in to change that /etc/modules file.

Thanks for your help.

Hi,

What's the RF connector on the wifi\bt board? U.fl?
Want to connect the board to a better antenna.
I think i picked up a mmcx cable and that didn't fit.

Thansk

I would love to see a touchscreen version or tablet to run a  chartplottter and digital dashboard on.  There is one good chartplotter app for Android, just need an economical and reliable platform.