Pine A64

I have tried searching but there doesn't seem to be much info on PPS support. It is a standard part of modern kernels and should be pretty consistent. On a Pine64+ using mainline kernel (debian-stretch-next) I chose an interrupt-enabled pin (PH9) updated /boot/armbianEnv.txt with overlays=pps-gpio uart1 uart2 param_pps_pin=PH9 and rebooted. I have a device (a GPS) with its PPS output connected to the Pi2 bus pin 13 that corresponds to PH9 and during boot this appears to be configured as a new PPS source: [ 5.548061] pps pps0: new PPS source pps@0.-1 [ 5.548135] pps pps0: Registered IRQ 145 as PPS source /dev/pps0 is indeed created by udev…

Has anyone gotten the ov5640 camera working with the SOPINE and baseboard? I'm using a prebuilt image from https://www.armbian.com/download/ - Armbian 5.38 stable Ubuntu 16.04.4 LTS 3.10.107-pine64 I've set camera_type=ov5640 in /boot/armbianEnv.txt and rebooted, but I'm having some trouble loading the camera module: Spoiler pi@pine64so:~$ sudo modprobe -r -f ov5640 pi@pine64so:~$ sudo modprobe -r -f vfe_v4l2 pi@pine64so:~$ sudo modprobe ov5640 pi@pine64so:~$ sudo modprobe vfe_v4l2 pi@pine64so:~$ dmesg [ 241.175358] [OV5640@lex]sensor_remove ov5640 sd = ffffffc076b9be00! [ 250.718969] [VFE]vfe_exit [ 250.719007] [VFE]vfe_runtime_resu…

Does anyone know where i can find linux headers for the LTS/Sopine, or an image that contains them? None of the images from the wiki seem contain the headers. I installed the Armbian legacy with 3.10.107 and was able to get Pine64 headers using apt-get install linux-headers-pine64 but they seem to be missing many files when i try to compile. Any help is greatly appreciated.

I am trying to port my app running on legacy OS to Mainline OS and found some problems: I was able to replicate problem with following actions: 1) git cloned fresh copy of source to new directory - OK 2) edited config-default.conf: KERNEL_ONLY="no" KERNEL_CONFIGURE="no" CLEAN_LEVEL="make,debs,oldcache,images" DEST_LANG="en_US.UTF-8" BOARD="pine64so" BRANCH="next" RELEASE="xenial" BUILD_DESKTOP="yes" KERNEL_KEEP_CONFIG="no" # do not overwrite kernel config before compilation EXTERNAL="no" # build and install extra applications and drivers EXTERNAL_NEW="prebuilt" …

Just for curiosity, I've updated my Armbian on my Pine64 to the latest release. The latest u-boot for Pine64 (U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:32:21) seems to have an issue with the persistent u-boot environment. Once I've written a custom environment back to MMC using `saveenv´ the board hangs during boot. Environment size: 10335/131068 bytes => saveenv Saving Environment to MMC... Writing to MMC(0)... done => reset resetting ... INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF INFO: AffInst: Level 0, MPID 0x3, State OFF …

Everytime i reboot and/or turn-off both of my Pine A64, they dont boot again until i manually turn-off/on them a lot of times, is there any fix to it? the img i use is: Armbian_5.35_Pine64_Debian_jessie_default_3.10.107.img

HI, I built the latest images for the Pine64+ & Pine64so - kernel 4.14.x + Debian 9 using the Armbian build scripts and had a problem with the ethernet not operational. Any help would greatly be appreciated. U-Boot SPL 2017.11-armbian (Dec 13 2017 - 23:42:42) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 23:41:50, Dec 13 2017 NOTICE: Configuring AXP PMIC NOTICE: PMIC: setup successful INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to no…

Hi, I'm trying to use the emmc device located on the Pine64LTS - not neccessarily to boot (though that would be nice). I'm employing a 16GB FORESEE card, which I obtained from the Pine folks. First I installed the Stable SoPine64 Armbian_5.30_Pine64so_Ubuntu_xenial_default_3.10.105 image from the Download web page. When I booted the image from an microSD card, only /dev/mmcblk0 showed up - no /dev/mmcblk1. When I tried to boot from the image loaded on the emmc card, the boot failed. Next I tried to build a more up-to-date image, using: git clone --depth 1 https://github.com/armbian/build cd build ./compile.sh And using the ch…

Running Armbian Ubuntu Xenial 16.04 on a PineA64, legacy kernel 3.10.105-pine64. Why is it necessary or desirable to put the variable 'ethaddr' in armbianEnv.txt? I thought the hardware mac address would be detected by the kernel. Perhaps not?

I have a feeling this was caused by a p[roblem with the definition of ftdfile variable: line from boot.cmd: load ${devtype} 0 ${fdt_addr_r} ${prefix}dtb/allwinner/${fdtfile} from the serial output: File not found /boot/dtb/allwinner/allwinner/sun50i-a64-pine64-plus.dtb ** note the duplication of Allwinner. Since I couldn't find where it was defined , I just copied the allwinner directory into itself.....:-) which fixed the problem. Perhaps someone could look into this? thanks.

Hello, today I made an upgrade of my pine64-mainline and failed miserably - my new armbian image won't boot any more. So I did some more tests with a new more different sd-cards, power supply and the mailine kernel form the download site (https://dl.armbian.com/pine64/Ubuntu_xenial_dev_nightly.7z): Again, the same behaviour, the image doesn't bott any more after "apt update" and "apt upgrade". Please, could someone help me with this problem? I hope these lockup logs help in troubleshooting. Thanks a lot! boot-fail-2017-09-06-A.log boot-fail-2017-09-06-B.log

Running Armbian Ubuntu Xenial 16.04 on a PineA64, legacy kernel 3.10.105-pine64. Why is it necessary or desirable to put the variable 'ethaddr' in armbianEnv.txt? I thought the hardware mac address would be detected by the kernel. Perhaps not?

Hi, After many attempt to installs and remove various version of teamviewer, I finally was able to make it run successfully. I try to use many architecture package even if they were not supposed to work. The running teamviewer is at the following link. I know it's not supposed to work but it is. https://download.teamviewer.com/download/linux/teamviewer-host_armhf.deb Here kind of command that I used randomly (I know, not really scientific approach!) sudo dpkg --add-architecture amd64 sudo dpkg --add-architecture i386 sudo apt-get install -f sudo apt-get update sudo dpkg --remove-architecture amd64 …

What's the current status of 5.30 on Pine64 mainline? I've a spare Pine64 lying around and was considering compiling latest Armbian for it to poke around a little, test things if that's useful to the dev effort. The downloads page lists support as experimental, but the version there is 5.27 and some of the info seems out of date, ie points to the wrong subforum, etc.

There was a huge thread a year ago about enabling SPI on Pine64, but it seemed to sometimes apply to longsleep generated kernel vs what I would think would be an out-of-the box build for Pine64 using the Armbian configuration. It wasn't clear to me exactly what needed to be done with today's build configuration, if anything. My ultimate goal is to integrate the IndustrialBerry ENC28J60 dual ethernet port card with Pine64. http://www.industrialberry.com/ethernetberry-v-1-1/ They have a recipe for RaspPi. I'm hoping there might be a similar type of recipe geared to the Pine64. Using the Armbian configurator, I insured the SPI bits were enabled (…

My Pine64 boots using Armbian_5.30_Pine64_Ubuntu_xenial_default_3.10.105_desktop. I have added pine64_lcd=on to /boot/armbianEnv.txt and updated the module file. But now when I plug in HDMI nothing displays on the HDMI screen. I also can not see it as a secondary display. Is it possible to have both displays on or can I only have one, having to remove LCD if I want HDMI output?

Hi have Armbian_5.30_Pine64_Ubuntu_xenial_default_3.10.105_desktop installed and it all works well. How do I configure it so that if no keyboard is plugged in that a virtual keyboard is displayed?

Pardon my noob question, I am still learning. I have been running Armbian on my Pine board for quite some time, now I would like to use it as a NAS. I really have no idea how or where start. thanks

I believe the TP-Link AC600 wireless usb adapter uses the Mediatek chipset. Has anybody got this running on a Pine A64?

I read in the documentation for the mainline kernel that the upper USB port is configured as OTG by default. ("It’s possible to convert the upper USB port (normally an OTG port) into a full USB host port using an own PHY by setting some magic bits.") See also the post of thkaiser: https://forum.armbian.com/index.php?/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/&tab=comments#comment-15074 Because I can use the upper USB port, I assume the "magic bits" were configured. But I had problems with the lower USB-Port. The output of "lsusb" gave me: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:…

I have Armbian up and running very nicely on the PineA64+ 2GB board. Thanks to the community! Speed concerns aside, is it possible to attach a SATA drive to this board? What would be the recommended way to do so? It is the availability of large storage capacity that we need for our project, not blazingly fast disk writes.

I'm guessing it wasn't intentional that the current legacy Armbian_5.30_Pine64_Ubuntu_xenial_default_3.10.105 image for the pine64 wouldn't work without the battery? Because the "Warning: Low battery power, shutting down to recharge" line (10th line from the end) is an absolute corker (or should I say showstopper?) when there is no battery connected to the pine64! It fell over on a 2G pine64 board that I was about to build up with Armbian. Spoiler HELLO! BOOT0 is starting! boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f boot0 version : 4.0.0 set pll start set pll end rtc[0] value = 0x00000000 rtc[1] value = 0x00000000 rtc[2] value = 0…

Hello! I installed a fresh Armbian (5.31; Server) on my Pine64 yesterday. Today I wanted to start playing around with GPIO ... And it seems like Pin 72 isn't working ... Doing the same on Pin 77, everything works fine ... For the secound test, I used https://github.com/databit/Pine64-CPP. I only added some Debug info to example.cpp. Spoiler Script started on Fri 28 Jul 2017 01:35:44 PM CEST root@pine64:/sys/class/gpio# echo "72" > export bash: echo: write error: Device or resource busy root@pine64:/sys/class/gpio# echo "72" > unexport bash: echo: write error: Invalid argument root@pine64:/sys/class/gpio# ls export gpi…

Hi, I've changed the default console from ttyS0 to ttyS3, using the mainline kernel with overlay "/boot/dtb/allwinner/overlay/sun50i-a64-uart3.dtbo". Unfortunately when I run command "sudo shutdown -r now" (or sudo reboot) my pine shuts down instead of reboot (although the console output says "reboot: Restarting system" at the end.) [Hard reset reboot works with "reboot -f" using ttyS3 console]. Using the standard console I can reboot my pine without problems. What could case this behavior? Is it necessary to disable or kill a ttyS3-process before the reboot?

Hi, I've tried to change the default console from ttyS0 to ttyS3, using the mainline kernel but I don't get it to work. Modifying boot.cmd I managed to change the tty's baudrate like this: "if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=ttyS0,38400"; fi" after recompiling with "mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr" it gave me an 38400-baud-output begining with line "Loading, please wait...starting version 229" But changing the settings to use ttyS3 does not work at all: "if test "${console}" = "serial" || test "${conso…

boot0 version : 4.0.0 set pll start set pll end rtc[0] value = 0x00000000 rtc[1] value = 0x00000000 rtc[2] value = 0x00000000 rtc[3] value = 0x00000000 rtc[4] value = 0x00000000 rtc[5] value = 0x00000000 DRAM driver version: V1.1 rsb_send_initseq: rsb clk 400Khz -> 3Mhz Set DRAM_VCC failed initializing SDRAM Fail. HELLO! BOOT0 is starting! boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f

Hi, just want share a little experiment I am doing to try to solve my Pine64 Boot Crash/Freeze Problem using a external (MCU) microcontroller to assist it. [MCU and Pine Drawing] [Actual Prototype Photo] The idea is very simple, just "watch" the SystemLED to detect if the system is booting normally, and if NOT, then issue a hardware reset, then, keeping repeating this process until the SystemLED indicates that the system is booting up... I am trying to document the process here is this tutorial page: http://www13.plala.or.jp/pskitty/copineon.html Files, source code, high quality pictures here on GitHub: h…

I am trying to display a bootlogo.bmp on boot without success. HDMI and also LCD. I don't mean the four tuxes (pines) on kernel load, i want to display it from u-boot. I am using Armbian 5.26 (don't know why kernel is 3.10.104), upgraded from 5.25. I have placed bootlogo.bmp on /boot but still nothing displayed by u-boot. All my u-boot builds also fails to display it. Has anyone tried it with success?

Hi!I am trying to connect B101UAN01.7 display(1920 x 1200) without any success.Is pine64's driver supports other display than native 7"? If so, then could you please help me to understand where can be error?Here is cutout from my device tree for 10.1" display lcd0@01c0c000 { compatible = "allwinner,sunxi-lcd0"; pinctrl-names = "active", "sleep"; status = "okay"; device_type = "lcd0"; lcd_used = <0x0>; lcd_driver_name = "mb709_mipi"; lcd_backlight = <0x32>; lcd_if …

[Photo of LED] http://www13.plala.or.jp/pskitty/img/pa64sysled/DSC_0045-photo-led.jpg [LED holes illustration] http://www13.plala.or.jp/pskitty/img/pa64sysled/pine64-drawing-v2-p6.jpg Hi, this is my first post here, after few first hours with Armbian on a 1G Pine64 board... I did a small initialization script to turn "ON" the System LED (upopulated "LED" label on the board), so that it helps to user to know that the boot process is running... I like to ask the dev team to think about including something like it to the Pine64 Armbian images, since the Pine64 board itself does not provide such indicator, the user is left in…

(One liner added later : the problem turned out to be the Cisco SOHO switch. They're "broken from the factory". Not what you'd expect, normally or in particular from Cisco.) Hi, everyone. I've taken the liberty of posting here with regard to my problem as I have the understanding the PINE64 forums proper are run by crazy people; my thought being to stay away from there. So, I have a 1 GB PINE64. I have ethernet performance problems - but NOT, I believe, in any way related to the early production models with their hardware fault or with gigabit ethernet being flakey. My PINE64 is in fact connected to a 100mbit hub, and is …

Are there any plans of creating an image incorporating an mainline 4.xxx kernel for the pine64 boards? Kernel.org states the projected EOL for the 3.10 kernel line as october 2017.

This is only my perception. I have this three SBC.: PINE 64 +, Nano PI A64, Banana pi M64. Everything on A64 allwinner chip. Armbian Image for Pine 64 works both Pine and Bananapi M64. But does not work NANO PI A64. Other third party software ( systems ) Remix, Ubuntu, work pine and banana pi and dont work nano pi. Only android 5.1.1 works on these three SBC....

The notes here, https://www.armbian.com/pine64/ talk about a beta image that has hardware acceleration enabled for the pine64. Unfortunately, the link is no longer valid. Anyone have a link to images I can use with the pine64 that have hardware (2d primarily) that i can use?

Hi. Is there no support for btrfs in the latest armbian-ubuntu-xenial for Pine64s? Linux pine54 3.10.104-pine64 #2 SMP PREEMPT Thu Feb 23 22:26:21 CET 2017 aarch64 aarch64 aarch64 GNU/Linux root@pine54:~# mkfs.btrfs /dev/sda1 btrfs-progs v4.4 See http://btrfs.wiki.kernel.org for more information. failed to open /dev/btrfs-control skipping device registration: No such file or directory Label: (null) UUID: d8362fb9-1b9c-4d92-8222-6745f842efcf Node size: 16384 Sector size: 4096 Filesystem size: 7.04GiB Block group profiles: Data: single 8.00MiB Metadata: DUP 368.62MiB Sys…

I am a bit lost how to create a bootable micro SD card with Armbian version for Pine64 board... I've downloaded Armbian_5.20_Pine64_Debian_jessie_3.10.102.7z file from Armbian site, extracted it using 7Zip on my Windows 7 machine and got following 6 files: armbian.txt armbian.txt.asc Armbian_5.25_Pine64_Debian_jessie_default_3.10.104.img Armbian_5.25_Pine64_Debian_jessie_default_3.10.104.img.asc sha256sum.sha AS I understiid, the *.img file is the disk image itself. However writing it to the SD card (using Etcher, as recommended, as well as Win32DiskImager that I've always used to write Pine64 images, then also tried with Rufus) renders t…

Found an interesting way to keep the Pine64 cool. https://www.youtube.com/watch?v=VFq1EbWOfYo

Hi everybody. Does anybody know how can i add the mali driver listed below to the latest Armbian image? Any suggestion would highly appreciated. http://wiki.pine64.org/index.php/Mali_Driver

If someone is interested i have compiled some TSLIB deb packages for the Pine64 Touch Screen to work without evdev driver or any other service behind. Advantages: * Easy to install (if you know how to edit xorg.conf) * No service needed * No calibration needed Disadvantages: * works on X11 only Information and deb packages: https://github.com/avafinger/pine64-touchscreen Hope it can be useful.

I suggest relevant discussion continues in this thread. I also urge mods to move relavant posts from here. What is Pinebook ? https://www.pine64.org/?page_id=3707 http://www.cnx-software.com/2016/11/24/pinebook-arm-linux-laptop-powered-by-allwinner-a64-processor-to-sell-for-89-and-up/

Hi, Wasn't sure where to start this as it's at-least potentially and partially off-topic regarding Armbian. First of all, thanks for what appears to be the best distro for the small ARM-soc devices, including the PINE64. I really appreciate all the work and houtrs that many people are dedicating to the project. Some history: The Logitech Squeezebox Touch was launched in April 2010) It has 4.3" colour touchscreen Connects to Logitech Media Server (LMS) through Ethernet or Wifi and plays songs stored there or from a wide range of internet sources. Supports 16- and 24-bit audio with a sampling rate of up to 96 kHz (or up to 192 kHz, enabled by us…

Hi, Not sure if this is me being stupid or a general problem with the 4.10 kernel: As there are now Mainline 4.10.0-next-20170125 images available from the main Pine64 download page, I tried flashing a spare card to start working on the touchscreen. Neither of the Server images based in 4.10 will boot on my board (no Ethernet activity so I can't ssh in). I also tried updating a working 3.10.104 / 5.25 installation with the dev. 4.x kernel, using the guide: Finally tried with a cross compiled kernel, built using the developer guide: https://docs.armbian.com/Developer-Guide_Build-Preparation/ All with same result: Board apparently doesn't b…

Hi, I have a pine64 with the official touch screen, currently running Xenial with legacy kernel. I followed the instructions to enable the touchscreen: Also starting with 5.24 Pine64’s own LCD with touchscreen support can simply be activated in /boot/armbianEnv.txt by setting pine64_lcd=on and adding gt9xxf_ts to /etc/modules followed by a reboot. which works fine. Preferably, I'd like to use a later kernel, as I'm not interested in any graphical HW acceleration but would like some of the other improvements in later kernels. When I tried the instructions with kernel 4.9, I couldn't find the gt9xxf_ts module. Is there any way of making this…

Hi, I was unable to get static MAC address working on my Pine64. I have the kernel boot argument, console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 panic=10 consoleblank=0 enforcing=0 loglevel=1 mac_addr=3a:bd:50:94:8b:06 But still, the from dmesg, [ 12.954581] sun8i-emac 1c30000.ethernet: device MAC address slot 0 aa:90:02:81:eb:e9 In the interfaces file, auto eth0 iface eth0 inet dhcp hwaddress ether 3a:bd:50:94:8b:06 But this caused error in ifup and system start up (networking cannot start since ifup failed with device in use) Although ifup failed, eth0 is visible in ifconfig, which means something else had already …

I tried to get armbian running on my new pine64. Therefore I downloaded the latest two 7z-files for debian and ubuntu. But neither of them does an auto-resize nor does the first boot took more than 30sec - contrary to the documentation. I'm using the SD cards delivered with the pine64 (16GB). In a related post I've found there has been "update-rc filesystem defaults" to (re-)trigger the process (or update.rc). Neither nor I've found. How can I get the distribution created in the correct way on the SD card?

Hey Igor and fellow Armbian forum members! I have worked with Armbian on my OPi PC and used the rtl8192cu-fixed github replacement driver, and recently just edited /etc/modules to include 8192cu(btw apt-get upgrade breaks this). However on my Pine64, dmesg says: rtlwifi/rtl8192cufw.bin isn't available. I have tried manually placing the Debian .bin file into the proper /lib but haven't been able to get the wlan0 to show up under iwconfig(yea I have already enabled it in /etc/network/interfaces. lsusb and lsmod both show some entries for 8912cu. Thanks for any insight, and let's hope we can fix this so that people can use their wifi adapters soon .

After flashing Armbian 5.20 to my SD card, running apt-get upgrade, it fails to boot with the new kernel. The last thing I get from the console is Image lacks image_size field, assuming 16MiB ## Loading init Ramdisk from Legacy Image at 45300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3845164 Bytes = 3.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 45000000 Booting using the fdt blob at 0x45000000 reserving fdt memory region: addr=45000000 size=200000 reserving fdt memory region: addr=41010000 size=10000 reserving fdt …

Hi, When will soon be ready for the Armbian Pine A64 Desktop Debian? Can I now install Debian xfce on the Armbian Pine A64 Server? and how? Thank you

Using legacy Xenial image on pine64, I found that VPN server could not be executed due to the lack of PPP and IPSEC kernel options and probably other modules. Could be enabled on future releases ? Best regards, Gustavo.

We have initial support for Pine64/Pine64+ for a long time in our repository but not released any official images yet. Since this will change soon a sneak preview what to expect. Hardware related issues: Please don't blame Armbian for the few design flaws Pine64 and Pine64+ show: These boards use Micro USB for DC-IN which is the worst possible decision. Most USB cables have a resistance way too high and are responsible for severe voltage drops when consumption increases, then the tiny Micro USB contacts have also a pretty high contact resistance and also maximum amperage for this connector is limited to 1.8A by USB specs. So in case you want …

Hi, Pine 64's delivery is in full swing and thousands of people are receiving/received their Pine64 boards (Mine is scheduled for May). One of the survey shows that majority of the people have chosen to install linux on their boards. Many people are struggling to find a good image for their boards and current some what stable image is based on already end of life 3.10 kernel and there is promising development by sunxi. I am sure that thousands will get benefited if they get Armbian for Pine64. So How about Armbian for Pine 64? Regards, -- Avinash

Hi, We are currently developing a low cost single board computer base on Allwinner A64 Processor. Please refer to the pine64.com and https://www.kickstarter.com/projects/pine64/577817754?token=12cf383f for more detail on the board. Currently we requesting open source community to participate and help to bring up Linux BSP to Ubuntu. Please let us know if you are interested. Thanks and regards, KH Goh