Hello!
Just as a disclaimer: I don't have an Pine, yet but I will buy one, soon.

I was wondering how to access the GPIO-Pins directly (like the PORT[...]-Registers on AVR or wiringPi for the Raspberry). How to set the Pins of PortL is written pretty detailed on Page 410 of the A64 User Manual. But what about the other Ports?

Thanks in advance!
Thomas131

I recently got a Pine 64 board along with a Power Cord, SD Card, Camera, Humidity Sensor. I have *somehow* misplaced the Power Cord & SD Card. I am oblivious as to how I done so but I did, sadly. 

Is it possible any of you could send me one via the mail? I live in the United States.

Need some basic help since the packaging didn't provide any clues and I haven't been able to find anything in my searches. I have the Openhab configuration with zwave card and serialapi_controller_static_ZW5304_USBVCP_US. 

Where does the Zwave card get 'plugged' into? 

The same question for the serialapi ... Also just guessing this provides a serial interface to get console access? Maybe useful if you are not connected to a lan?  

Also it looks like they shipped a push button but don't know the use of this or where it would get 'plugged' in. Guessing it is some sort of reset button so you don't need to pull the power.

Thanks

Since I was mostly busy with my job and other things over the last couple month I only just recently came back to my Pine64 projects. I then was looking at the currently available Linux support options and found that Armbian now has official support for the Pine64. I am currently running one of their Ubuntu images with BSP kernel and an experimental one with an updated mainline (sunxi) kernel.

You can find more information and images at their Download site: https://www.armbian.com/pine64/
Make sure to read all the hints and issues which nicely sums up most things you need to be aware of or configure to your needs: https://docs.armbian.com/board_details/pine64/

While the download section has ready built images, Armbian is by design a build system which creates Debian/Ubuntu based images for ARM systems and you can roll your own  with custom configuration as well:  https://docs.armbian.com/Developer-Guide...eparation/

I would like to collect information and feedback from other Armbian users here.

I am following the instructions on the GitHub page to try and install Windows 10 IoT on my Pine, but they're really not making this easy. Besides some poorly worded and confusing instructions in steps 2 and 3, it says I am supposed to open the iothub_csharp_client.sln solution (/azure-iot-sdks/csharp) file. However, that file does not even exist in the repository.

Also, there are two different URLs to download the .ffu file specified between this forum and the GitHub page — http://files.pine64.org/os/win10-iot/Win...Pine64.ffu and http://files.pine64.org/os/win10-iot/Pin...eta0.1.ffu. This level of inconsistency is staggering.

Has anyone else run into these issues? If so, how were able to get around them? I don't know where to go from here.

Thanks.

I suspect the answer is yes, since some people use their PINE as a server.   But I have mine set up with android 6, and since the keyboard has to be plugged in after booting... is it okay to just never tune the PINE off?

I was attempting to rebuild the EFI to support win10 core.
I followed the instructions at:https://github.com/Leeway213/WinIoTBoot

I am running under Ubuntu 16 (64bit) as the Windows build is not supported yet.

After executing the ./build.sh script in the SunxiPlatformPkg directory and answering the target questions it failed because the "C" directory
in the base tools source folder is not present. I copied the "C" folder from the edk2 master repo and it rebuild tools now on launch of same script but now I get the
following error:
Build start time: 09:25:01, Jan.07 2017
WORKSPACE        = /home/david/edk2
ECP_SOURCE       = /home/david/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /home/david/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /home/david/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /home/david/edk2/BaseTools

Architecture(s)  = ARM
Build target     = RELEASE
Toolchain        = ARMLINUXGCC
Active Platform          = /home/david/edk2/SunxiPlatformPkg/sun50iw1p1Pkg/sun50iw1p1Pkg.dsc
Flash Image Definition   = /home/david/edk2/SunxiPlatformPkg/sun50iw1p1Pkg/sun50iw1p1Pkg.fdf
Processing meta-data ............. done!
Building ... /home/david/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [ARM]
"/home/david/edk2/SunxiPlatformPkg/pctools/toolchain/gcc-linaro/bin/arm-linux-gnueabi-gcc" -march=armv7-a -mfpu=neon -I/home/david/edk2/SunxiPlatformPkg/sun50iw1p1Pkg/Include/Sun50iW1P1 -g -O2 -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-missing-braces -Wno-array-bounds -c -include AutoGen.h -mword-relocations -mlittle-endian -mabi=aapcs -mapcs -fno-short-enums -save-temps -fsigned-char -ffunction-sections -fdata-sections -fomit-frame-pointer -Wno-address -mfloat-abi=soft -fno-stack-protector -mno-unaligned-access -Wno-unused-but-set-variable -DCONFIG_ARCH_SUN50IW1P1 -o /home/david/edk2/Build/SunxiPlatform/sun50iw1p1Pkg/RELEASE_ARMLINUXGCC/ARM/MdePkg/Library/BasePcdLibNull/BasePcdLibNull/OUTPUT/./PcdLib.obj -I/home/david/edk2/MdePkg/Library/BasePcdLibNull -I/home/david/edk2/Build/SunxiPlatform/sun50iw1p1Pkg/RELEASE_ARMLINUXGCC/ARM/MdePkg/Library/BasePcdLibNull/BasePcdLibNull/DEBUG -I/home/david/edk2/MdePkg -I/home/david/edk2/MdePkg/Include -I/home/david/edk2/MdePkg/Include/Arm /home/david/edk2/MdePkg/Library/BasePcdLibNull/PcdLib.c
/bin/sh: 1: /home/david/edk2/SunxiPlatformPkg/pctools/toolchain/gcc-linaro/bin/arm-linux-gnueabi-gcc: not found
GNUmakefile:316: recipe for target '/home/david/edk2/Build/SunxiPlatform/sun50iw1p1Pkg/RELEASE_ARMLINUXGCC/ARM/MdePkg/Library/BasePcdLibNull/BasePcdLibNull/OUTPUT/PcdLib.obj' failed
make: *** [/home/david/edk2/Build/SunxiPlatform/sun50iw1p1Pkg/RELEASE_ARMLINUXGCC/ARM/MdePkg/Library/BasePcdLibNull/BasePcdLibNull/OUTPUT/PcdLib.obj] Error 127

build.py...
 : error 7000: Failed to execute command
 make --no-print-directory tbuild [/home/david/edk2/Build/SunxiPlatform/sun50iw1p1Pkg/RELEASE_ARMLINUXGCC/ARM/MdePkg/Library/BasePcdLibNull/BasePcdLibNull]

build.py...
 : error 7000: Failed to execute command
 make --no-print-directory tbuild [/home/david/edk2/Build/SunxiPlatform/sun50iw1p1Pkg/RELEASE_ARMLINUXGCC/ARM/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull]

build.py...
 : error F002: Failed to build module
 /home/david/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [ARM, ARMLINUXGCC, RELEASE]
- Failed -
Build end time: 09:25:15, Jan.07 2017
Build total time: 00:00:14

I can not understand this error. the arm-linux-gnueabi-gcc is clearly in the pctools/toolchain directory and it has the executable attribute.

Any help?

Im trying to get Openhab2 to run on my Pine64 with my Aeon Zwave gen5 stick.
Lots of problems with the the device not found. If I use the openHAB Image 20160915 base on Ubuntu Linux Longsleep image everything works great.
The problem is I would like to use Debian Base (3.10.102 BSP 2).
I have seen that I must use 32bit java so it will work.
Looked everywhere for a 32 bit version for the pine64. There is so many different versions and so confusing.
Would anyone know the steps I need to do to get it working?

I seem to have forgotten which one it was that I bought. How can I find out which model I have, as well as the complete specs?

Hi,

I'm making some tests with external harddrive with LVM2 and I need pvmove... but it won't work without dm-mirror. I've checked and this kernel module isn't enabled. So I downloaded the kernel source from (https://github.com/longsleep/build-pine6...ter/kernel) and proceeded to check the dm-mirror module with the menuconfig. Once completed I then made a (make modules) and copied the module in /lib/module/... folder.

Now if I do depmod && modprobe dm-mirror it complains that the format is invalid. I neved had that knind of error... unless I was cross compiling wich i'm not since I built the module on the pine itself.

The exact error is :

modprobe: ERROR: could not insert 'dm_mirror': Exec format error

Any idea about how to fix the problem?