Difference between revisions of "Main Page"

From PINE64
Jump to navigation Jump to search
(41 intermediate revisions by 4 users not shown)
Line 1: Line 1:


== What You’ll Need to Get Started ==
== What You’ll Need to Get Started ==
You will need the following to get started with using your Pine A64 or A64+ board:
* Windows / Linux PC or MAC with a SD Card Reader connected to the Internet
* Power Supply (PSU) and a micro usb cable. Please make sure to use a PSU rated at +5V @2A and a micro USB cable that is at least 26 AWG thick.
* MicroSD card (8GB or higher capacity) rated 'class 10' or better.
* HDMI cable (unless you wish to run headless / without a monitor). '''N.B'''. Android and Remix OS support 720p and 1080p, while Linux supports a [https://github.com/longsleep/sunxi-disp-tool#available-hdmi-output-names wider range of resolutions].
* Input device(s) such as: keyboard, mouse, remote, pointer, etc.




You will need the following to get started with using your Pine A64 or A64+ board:
*Windows / Linux PC or MAC with a SD Card Reader connected to the Internet
*Power Supply (PSU) and a micro usb cable. Please make sure to use a PSU rated at +5V @2A and a micro USB cable that is at least 26 AWG thick.
*MicroSD card (8GB or higher capacity) rated 'class 10' or better.
*HDMI cable (unless you wish to run headless/ without a monitor). '''N.B'''. Android and Remix OS support 720p and 1080p, while Linux supports a [https://github.com/longsleep/sunxi-disp-tool#available-hdmi-output-names wider range of resolutions].
*Input device(s) such as: keyboard, mouse, remote, pointer, etc,.


== Step by Step Instructions ==
== Step by Step Instructions ==
Line 14: Line 15:
'''Caution!'''
'''Caution!'''


Please handle the Pine A64 or A64+ with care. Always hold the board by the edges and make sure to wear an antistatic wrist strap when handling the Pine A64 (+). Touching components on the front and back of the board can result in an ESD discharge that may damage your board. Avoid placing the board on materials such as carpets, plastics or other surfaces prone to electrostatic build-up.
Please handle the Pine A64 or A64+ with care. Always hold the board by the edges and make sure to wear an anti-static wrist strap when handling the Pine A64 (+). Touching components on the front and back of the board can result in an ESD discharge that may damage your board. Avoid placing the board on materials such as carpets, plastics or other surfaces prone to electrostatic build-up.




Line 22: Line 23:


Please refer to the relevant section below for instructions on how to image your microSD card:
Please refer to the relevant section below for instructions on how to image your microSD card:
*[[#Imaging microSD on Windows 7/8/8.1/10]]
* [[#Imaging microSD on Windows 7/8/8.1/10|Imaging microSD on Windows 7/8/8.1/10]]
*[[#Imaging microSD on Apple OSX]]
* [[#Imaging microSD on Apple OSX|Imaging microSD on Apple OSX]]
* [[#Imaging microSD on Linux|Imaging microSD on Linux]]


Having successfully imaged your microSD card, insert it into the microSD slot located at the bottom left of the board / to the left of the USB 2.0 sockets.
Having successfully imaged your microSD card, insert it into the microSD slot located at the bottom left of the board / to the left of the USB 2.0 sockets.
Line 30: Line 32:
'''Plug in the HDMI Cable, Ethernet Cable and Peripherals'''
'''Plug in the HDMI Cable, Ethernet Cable and Peripherals'''


Unless you are planning on running your Pine A64 (+) headless (without a monitor / as a server), you should plug in all necessary peripherals, including the HDMI and Ethernet cable, prior to powering on the board. Do note, depending on which OS image you are using, some peripherals may or may not work. '''N.B.''' [http://forum.pine64.org/showthread.php?tid=1127 Some HDMI→DVI/ VGA converters may not work] in conjunction with your monitor or TV.
Unless you are planning on running your Pine A64 (+) headless (without a monitor / as a server), you should plug in all necessary peripherals, including the HDMI and Ethernet cable, prior to powering ON the board. Do note, depending on which OS image you are using, some peripherals may or may not work. '''N.B.''' [http://forum.pine64.org/showthread.php?tid=1127 Some HDMI→DVI/VGA converters may not work] in conjunction with your monitor or TV.




'''Apply Power to Your Board'''
'''Apply Power to Your Board'''


Once you have imaged your microSD and plugged everything in, you are ready to apply power to the Pine A64(+) board. You'll need a good quality 5 Volt, 2 Amp PSU. Using a good quality PSU and micro USB cable is very important as failing to meet the required specifications may prevent the board from booting correctly. A marginally higher PSU Voltage is acceptable (for instance, 5.1 volts - due to the nature of the micro usb connection, a 5.1v supply can help protect slightly against voltage drops which can cause undesirable results). However, a significantly higher voltage of 7 Volts or more will damage the Pine A64(+) board and may render it inoperative.
Once you have imaged your microSD and plugged everything in, you are ready to apply power to the Pine A64(+) board. You'll need a good quality 5 Volt, 2 Amp PSU. Using a good quality PSU and micro USB cable is very important as failing to meet the required specifications may prevent the board from booting correctly. A marginally higher PSU Voltage is acceptable (for instance, 5.1 volts - due to the nature of the micro usb connection, a 5.1v supply can help protect slightly against voltage drops which can cause undesirable results). However, a significantly higher voltage of 7 Volts or more will damage the Pine A64(+) board and may render it inoperative.


If you are using a separate micro USB cable with your PSU, make sure that the cable has a low resistance rating. Cables with high resistance will cause improper function and the unit may not boot at all or only partially. The thicker the internal cabling, the better [http://voyager8.blogspot.co.uk/2013/04/how-to-choose-good-usb-data-and.html i.e. AWG (American Wire Gauge) 20 is better than AWG 28]. In General, power-only microUSB cables come with red colour USB header.
If you are using a separate micro USB cable with your PSU, make sure that the cable has a low resistance rating. Cables with high resistance will cause improper function and the unit may not boot at all or only partially. The thicker the internal cabling, the better [http://voyager8.blogspot.co.uk/2013/04/how-to-choose-good-usb-data-and.html i.e. AWG (American Wire Gauge) 20 is better than AWG 28]. In General, power-only microUSB cables come with red colour USB header.
Line 42: Line 44:




===Imaging microSD on Windows 7/8/8.1/10===
 
=== Imaging microSD on Windows 7/8/8.1/10 ===




You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
*A compression Utility (used to unarchive the OS image). We recommend you use [http://www.7-zip.org/download.html 7zip].
* A compression Utility (used to unarchive the OS image). We recommend you use [http://www.7-zip.org/download.html 7zip].
*A disk image utility (used to ‘burn’ the .img to your SD card). We recommend you use either the [https://sourceforge.net/projects/win32diskimager/ Win32Imager] or [https://etcher.io/ Etcher] utility.
* A disk image utility (used to ‘burn’ the .img to your SD card). We recommend you use either the [https://sourceforge.net/projects/win32diskimager/ Win32Imager] or [https://etcher.io/ Etcher] utility.
'''Optional'''
'''Optional'''
*Phoenix Card image utility (used ONLY for phoenix card images). You can download it from [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing here].
* Phoenix Card image utility (used ONLY for phoenix card images). You can download it from [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing here].




'''Downloading and extracting OS image(s)'''
'''Downloading and extracting OS image(s)'''


You can find all curated OS images under [[#Curated Pine A64 (A64+) OS Images]].
You can find all curated OS images under [[#Curated Pine A64 (A64+) OS Images|Curated Pine A64 (A64+) OS Images]].
There are two type of Android and Remix images available. Images designated ‘DD’ need to be imaged using Etcher or Win32imager, whilst images labelled ‘Phoenix Card Image’ require the Phoenix Card utility.
There are two type of Android and Remix images available. Images designated ‘DD’ need to be imaged using Etcher or Win32imager, whilst images labelled ‘Phoenix Card Image’ require the Phoenix Card utility.


Having downloaded the required OS image proceed to use 7zip to unarchive it by right-clicking the archive, and sellecting ‘Extract All’. Upon completion, note the destination of where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.
Having downloaded the required OS image proceed to use 7zip to unarchive it by right-clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination of where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.




'''Imagining the microSD card (DD)'''
'''Imaging the microSD card (DD)'''


*Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.
* Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.


*Launch Win32diskImager.exe or etcher.exe. You will be presented with a field titled ‘path’ and a drop down menu labeled ‘device’. Click the ‘path’, navigate to and select the OS image you extracted from the archive earlier. Next, from the drop-down menu select the drive your microSD has been assigned. N.B. Pay close attention to the selected drive (remember your letter) – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
* Launch Win32diskImager.exe or etcher.exe. You will be presented with a field titled ‘path’ and a drop down menu labeled ‘device’. Click the ‘path’, navigate to and select the OS image you extracted from the archive earlier. Next, from the drop-down menu select the drive your microSD has been assigned. '''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.


*Having chosen the desired OS image and the correct driver press ‘write’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from Windows.
* Having chosen the desired OS image and the correct driver press ‘write’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from Windows.




Line 73: Line 76:
On Windows, you can also use Phoenix Card (for detailed instructions click [http://wiki.pine64.org/index.php/PhoenixCard here]). The Phoenix Card utility works ONLY with images designated as ‘Phoenix Card’ in the downloads section. To use Phoenix Card follow these steps:
On Windows, you can also use Phoenix Card (for detailed instructions click [http://wiki.pine64.org/index.php/PhoenixCard here]). The Phoenix Card utility works ONLY with images designated as ‘Phoenix Card’ in the downloads section. To use Phoenix Card follow these steps:


*Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.
* Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.


*Launch phoenixcard.exe. You will be presented with a ‘disk’ drop-down menu and a field denoted as ‘Img File’. Click on ‘Img File’ and navigate to and select the OS image have downloaded and unarchived. Next, make sure to select the disk that your microSD card has been assigned. N.B. Pay close attention to the selected drive (remember your letter) – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
* Launch phoenixcard.exe. You will be presented with a ‘disk’ drop-down menu and a field denoted as ‘Img File’. Click on ‘Img File’ and navigate to and select the OS image have downloaded and unarchived. Next, make sure to select the disk that your microSD card has been assigned. '''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.


*Make sure to select ‘Startup!’ from the ‘Write mode’ window and click Burn. Once the image has been written to your microSD card you will receive a confirmation in the ‘option’ window. Be sure to close the application and to eject/remove your SD card safely from Windows.
* Make sure to select ‘Startup!’ from the ‘Write mode’ window and click Burn. Once the image has been written to your microSD card you will receive a confirmation in the ‘option’ window. Be sure to close the application and to eject/remove your SD card safely from Windows.


===Imaging microSD on Apple OSX===


----
=== Imaging microSD on Apple OSX ===


You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
 
* A compression Utility (used to unarchive the OS image). We recommend you use [http://www.7-zip.org/download.html 7Zip].
*A compression Utility (used to unarchive the OS image). We recommend you use [http://www.7-zip.org/download.html 7Zip].
* A disk image utility (used to ‘burn’ the .img to your SD card in GUI). We recommend you use [http://mac.softpedia.com/get/Utilities/ApplePi-Baker.shtml#download ApplePi Baker] or [https://etcher.io/ Etcher].
*A disk image utility (used to ‘burn’ the .img to your SD card in GUI). We recommend you use [http://mac.softpedia.com/get/Utilities/ApplePi-Baker.shtml#download ApplePi Baker] or [https://etcher.io/ Etcher].




Line 93: Line 96:
'''Downloading and extracting OS image(s)'''
'''Downloading and extracting OS image(s)'''


You can find all curated OS images under [[#Curated Pine A64 (A64+) OS Images]]. On OSX you can only use images designated as ‘DD’.
You can find all curated OS images under [[#Curated Pine A64 (A64+) OS Images|Curated Pine A64 (A64+) OS Images]]. On OSX you can only use images designated as ‘DD’.


Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.
Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.




'''Imagining the microSD card (GUI)'''
'''Imaging the microSD card (GUI)'''


*Insert your microSD card into your Mac laptop/USB card reader. You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
* Insert your microSD card into your Mac laptop/USB card reader. You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.


*Launch Apple-Pi Baker or the etcher utility. Upon startup the application it will ask for your password. When the application launches you will be presented with a field titled ‘IMG file’ and a path of the mounted microSD card (it will look something like this: ‘/dev/diskX 32.0Gb SD card’). Click the ‘IMG file’ button, navigate to and select the OS image you extracted from the archive earlier. Next, select the microSD from the window. N.B. Pay close attention to the selected drive – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
* Launch Apple-Pi Baker or the etcher utility. Upon startup the application it will ask for your password. When the application launches you will be presented with a field titled ‘IMG file’ and a path of the mounted microSD card (it will look something like this: ‘/dev/diskX 32.0Gb SD card’). Click the ‘IMG file’ button, navigate to and select the OS image you extracted from the archive earlier. Next, select the microSD from the window. '''N.B.''' Pay close attention to the selected drive – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.


*Having chosen the desired OS image and the correct driver press ‘Restore Backup’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your Mac.
* Having chosen the desired OS image and the correct driver press ‘Restore Backup’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your Mac.




Line 111: Line 114:
'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.
'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.


*Insert your microSD card into your Mac laptop/USB card reader. You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
* Insert your microSD card into your Mac laptop/USB card reader. You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.


*Open up your terminal and navigate to the directory where you unarchived your OS image.
* Open up your terminal and navigate to the directory where you unarchived your OS image.
*Before you start writing to the card, you will have to identify your microSD card. Type: diskutil list and note the output. The disk number should match the size of your SD card and will likely be using ‘Fdisk_partition_scheme’. Having identified the disk number execute the following commands (substitute diskX for your disk and name of image for pine64-image-name.img):
 
* Before you start writing to the card, you will have to identify your microSD card. Type: diskutil list and note the output. The disk number should match the size of your SD card and will likely be using ‘Fdisk_partition_scheme’. Having identified the disk number execute the following commands (substitute diskX for your disk and name of image for pine64-image-name.img):


''diskutil unmountDisk /dev/diskX
''diskutil unmountDisk /dev/diskX
sudo dd if=pine64-image-name.img of=/dev/disk2 bs=1M''
sudo dd if=pine64-image-name.img of=/dev/disk2 bs=1M''


*Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your Mac.
* Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your Mac.
 
 
----
=== Imaging microSD on Linux ===
 
You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
* A compression Utility (used to unarchive the OS image). We recommend you use [http://www.7-zip.org/download.html 7Zip].
* A disk image utility (used to ‘burn’ the .img to your SD card in GUI). We recommend you use [https://etcher.io/ Etcher] or the [https://git.gnome.org/browse/gnome-disk-utility/ GUI Disks utility] that ships with most popular distros.
 
 
'''N.B.''' Phoenix Card utility and images are NOT available on Linux.
 
 
'''Downloading and extracting OS image(s)'''
 
You can find all curated OS images under [[#Curated Pine A64 (A64+) OS Images|Curated Pine A64 (A64+) OS Images]]. On Linux you can only use images designated as ‘DD’.
 
Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.
 
 
'''Imaging the microSD card (GUI)'''
 
* Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in your File Manager / on your desktop.
 
* Launch Disks or the etcher utility (This tutorial outlines how to use Disks, if you wish to learn how to use Etcher please visit [https://etcher.io/ their website]).
 
* Upon launching Disks, you will be presented with all volumes visible to your computer. As a rule of thumb, your microSD card should be found at the bottom of listed volumes. Verify this by checking the size and mounting of the microSD card. '''N.B.''' Pay close attention to the selected drive – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
 
* Having selected your microSD card, click the cog menu in top right corner and choose the ‘Restore Disk Image’ option from the drop-down list. Navigate to and select the OS image you extracted from the archive earlier. Once you select it, you will be asked to enter your password and to confirm writing to the chosen volume (microSD card).
 
* You will be given a predicted time, writing-speed and completion percentage. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your computer.
 
 
'''Imaging from Terminal'''
 
'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.
 
* Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
* Open up your terminal and navigate to the directory where you unarchived your OS image.
* Before you start writing to the card, you will have to identify your microSD card.
* Type: ''lsblk'' and pay attention to the listed disks. Disks will appear as ''/dev/sda /dev/sdb'' etc. Look at the drive that matches your microSD card’s size.
* Having located the microSD card use the following command to burn the .img of choice to the microSD card (/dev/sdb used as example): ‘’sudo unmount /dev/sdb1''
* Now you are ready to write the image to the microSD card using this command: ‘’sudo dd if=pine64_image_name.img of=/dev/sdb bs=1M''
* Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your computer.
 




== Troubleshooting ==
== Troubleshooting ==
There is a number of things that can prevent the Pine A64(+) board from booting up properly. The most common culprits of a failed boot are (to find out more click [http://forum.pine64.org/showthread.php?tid=514 here]):  
There is a number of things that can prevent the Pine A64(+) board from booting up properly. The most common culprits of a failed boot are (to find out more click [http://forum.pine64.org/showthread.php?tid=514 here]):  


*Subpar or counterfeit microSD card
* Subpar or counterfeit microSD card
*Subpar Power Supply
* Subpar Power Supply
*High resistance (thin) or a very long microUSB cable
* High resistance (thin) or a very long microUSB cable
*Failed imaging of the microSD card (refer to  the respective ‘imaging microSD card section)  
* Failed imaging of the microSD card (refer to  the respective ‘imaging microSD card section)  


Make sure to have the newest version of the OS image your are running. On Linux, you can update the kernel and uboot using scripts located in the following directory: /usr/local/sbin  
Make sure to have the newest version of the OS image your are running. On Linux, you can update the kernel and uboot using scripts located in the following directory: /usr/local/sbin


To navigate to the directory type (in terminal): ''cd /usr/local/sbin''  
* To navigate to the directory type (in terminal): ''cd /usr/local/sbin''  
 
* You list all the available scripts by typing (in terminal): ''ls''  
You list all the available scripts by typing (in terminal): ''ls''  
* To run the script required update script run the following command: ''sudo ./update_script.sh'' (substitute the relevant update script for update_script)  
 
To run the script required update script run the following command: ''sudo ./update_script.sh'' (substitute the relevant update script for update_script)  




'''Supported Screen Resolutions'''
'''Supported Screen Resolutions'''


The pine supports a number of video resolutions under Linux, however RemixOS and Android images currently only support '''720p''' and '''1080p'''. Linux supports a wider range of resolutions (see all resolutions supported on Linux [https://github.com/longsleep/sunxi-disp-tool#available-hdmi-output-names here]). If the native resolution of your monitor or TV is not compatible with the Pine A64(+) then you will be unable to get a video to work with your screen.  
The pine supports a number of video resolutions under Linux, however RemixOS and Android images currently only support '''720p''' and '''1080p'''. Linux supports a wider range of resolutions (see all resolutions supported on Linux [https://github.com/longsleep/sunxi-disp-tool#available-hdmi-output-names here]). If the native resolution of your monitor or TV is not compatible with the Pine A64(+) then you will be unable to get a video to work with your screen.




Line 148: Line 196:
Follow these steps to determine the cause of your problem:  
Follow these steps to determine the cause of your problem:  


*Check your PSU and microUSB cable ratings
* Check your PSU and microUSB cable ratings
*Download and image a base image of Linux   
* Download and image a base image of Linux   
*Plug in Power and Ethernet into your Board
* Plug in Power and Ethernet into your Board
*Watch Ethernet port LED activity
* Watch Ethernet port LED activity
*Check your router for Pine A64(+) IP
* Check your router for Pine A64(+) IP
*Attempt to ssh into the Pine A64(+) from your computer
* Attempt to ssh into the Pine A64(+) from your computer


If your PSU and microUSB meet the criteria, and you have correctly followed the instructions to image your card and power on the board, but you are not seeing any LED activity and cannot ssh into your Pine A64(+) then either the imaging process failed (possibly due to a subpar microSD) OR the PSU / microUSB cable is/are faulty.
If your PSU and microUSB meet the criteria, and you have correctly followed the instructions to image your card and power on the board, but you are not seeing any LED activity and cannot ssh into your Pine A64(+) then either the imaging process failed (possibly due to a subpar microSD) OR the PSU / microUSB cable is/are faulty.
Line 159: Line 207:
If your PSU and microUSB meet the criteria, and you have correctly imaged the OS to your card and power on the board and your can ssh into your Pine A64(+) but get no video feed, then it's likely that the native resolution of your monitor/TV is not supported.  
If your PSU and microUSB meet the criteria, and you have correctly imaged the OS to your card and power on the board and your can ssh into your Pine A64(+) but get no video feed, then it's likely that the native resolution of your monitor/TV is not supported.  


If neither of the abovementioned scenarios fits the problem you are facing please consult this thread (thanks to Ghost for compiling the list): http://forum.pine64.org/showthread.php?tid=680
If neither of the above mentioned scenarios fits the problem you are facing, please consult this thread (thanks to Ghost for compiling the list): http://forum.pine64.org/showthread.php?tid=680


If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/
If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/




== Curated Sopine OS Images  ==
=== Ubuntu ===
* '''Ubuntu Desktop Image [20170306] built by Pine64'''
[[File:Logo_ubuntu.jpg]]
** '''This is a build including DE based on longsleep works and may not have all the up-to-date features offered by longsleep and Sunxi community'''. For latest build, you can create one and [http://forum.pine64.org/showthread.php?tid=376 following this thread]
** This build optimizes Gigabit Ethernet parameter and improves on GbE connectivity.
** Included Mate Desktop, Firebox Browser, and LibreOffice Suite.
** Included libvdpau-sunxi with SMPlayer
** Included with Wifi and Bluetooth
** Included library set that provides access to the GPIO headers in Linux as provided by community member KB3VGW (https://devhub.io/repos/kb3vgw-wiringPi-Pine64)
** Not yet optimize for Graphic acceleration
** Suitable for Sopine Board only
* Login with
** username: ubuntu
** password: ubuntu
* Auto execute resize_rootfs.sh script on first boot-up to resize the root partition in order to fully utilize the SD Card
* DD image (for 8GB micoSD card and above):
*** [http://files.pine64.org/os/SOPINE/ubuntu/xubuntu-xenial-mate-20170306-longsleep-sopine-8GB.img.gz Direct download from pine64.org]
*** MD5 (Zip file): 67E3CBF695AB4196C00F205AEB0F3623
*** File Size: 2.09GB
=== Android ===
* '''Android 6.0.1 Image [20170331]'''
* DD image (for 8GB microSD Card)
*** [http://files.pine64.org/os/SOPINE/android/android-rooted-ver6.0.1-20170331-sopine-8GB.img.gz Direct download from pine64.org]
*** MD5 (Zip file): 4936361E31EDC1E4BA44FBAC08C1619F
*** File Size: 951MB
* DD image (for 16GB microSD Card)
*** [http://files.pine64.org/os/SOPINE/android/android-rooted-ver6.0.1-20170331-sopine-16GB.img.gz Direct download from pine64.org]
*** MD5 (Zip file): BF27C58001C1CEA02CECA9082BD8BC41
*** File Size: 936MB
* DD image (for microSD Card to eMMC)
*** Burn this image to a 8GB microSD Card, insert into SOPINE and it will start program to eMMC.  The power LED will be turn off when the process is completed.  Unplug the MicroSD card from SOPINE to boot from eMMC.
*** [http://files.pine64.org/os/SOPINE/android/android-ver6.0.1-rooted-20170331-sopine-sd2emmc-lpddr3.img.gz Direct download from pine64.org]
*** MD5 (Zip file): 99736D857E675254D4C3ACA95024B3F3
*** File Size: 673MB
* '''Android 5.1.1 Image [20160630]'''
* DD image (for 8GB microSD Card)
*** [http://files.pine64.org/os/SOPINE/android/android-ver5.1.1-20160630-sopine-8GB.img.gz Direct download from pine64.org]
*** MD5 (Zip file): D5A5CE806D6E65F6F841E9E1711A6B77
*** File Size: 681MB


== Curated Pine A64 (A64+) OS Images  ==
== Curated Pine A64 (A64+) OS Images  ==


=== Debian Jessie ===
=== Debian Jessie ===
 
* '''Debian Jessie Linux by Lenny Raposo (Longsleep kernel 3.10.102 BSP 2)'''
*'''Debian Jessie Linux by Lenny Raposo (Longsleep kernel 3.10.102 BSP 2)'''
[[File:Logo_debian.jpg]]
[[File:Logo_debian.jpg]]
** DD image (for 8GB and above SD Card):
** DD image (for 8GB and above SD Card):
*** [http://forum.pine64.org/showthread.php?tid=497&pid=4292#pid4292 Lenny's Debian Support thread on Pine64 forum]
*** [http://forum.pine64.org/showthread.php?tid=497&pid=4292#pid4292 Lenny's Debian Support thread on Pine64 forum]
*** [https://www.pine64.pro/downloads/#Debian-Linux Link to all available Debian versions]
*** [http://cdn.pine64.uk Link to all available Debian versions]
*** File Size: 1.1GB
*** File Size: 1.1GB
** Up to date on longsleep uboot, kernel and fixes
** Up to date on longsleep uboot, kernel and fixes
Line 181: Line 273:
*** password: debian
*** password: debian
** '''Execute resize_rootfs.sh''' script to resize the root partition in order to fully utilize the SD Card
** '''Execute resize_rootfs.sh''' script to resize the root partition in order to fully utilize the SD Card


=== Ubuntu 16.04 ===
=== Ubuntu 16.04 ===
 
* '''Ubuntu Linux Image by Longsleep (3.10.xxx)'''
*'''Ubuntu Linux Image by Longsleep (3.10.xxx)'''
[[File:Logo_ubuntu.jpg]]
[[File:Logo_ubuntu.jpg]]
** Thanks to longsleep's work, the Linux build progress rapidly. For latest build please see [http://forum.pine64.org/showthread.php?tid=376 this thread]
** Thanks to longsleep's work, the Linux build progress rapidly. For latest build please see [http://forum.pine64.org/showthread.php?tid=376 this thread]
Line 197: Line 289:
** '''Execute resize_rootfs.sh''' script to resize the root partition in order to fully utilize the SD Card
** '''Execute resize_rootfs.sh''' script to resize the root partition in order to fully utilize the SD Card


=== Android 5.1.1 ===


*'''Android 5.1.1 Image Release 20160711 [v1.2.6]'''
=== Android 6.0 ===
[[File:Logo_android_lollipop.jpg]]
* '''Android 6.0 Image (HDMI Video Output) Release 20170112 [ver 2.0.1]'''
[[File:Logo_android_marshmallow.jpg]]
** The Android build is suitable for 1GB/2GB Pine A64+ Board but not advised to run on a 512MB Pine A64 Board due to system memory constraints.
** The Android build is suitable for 1GB/2GB Pine A64+ Board but not advised to run on a 512MB Pine A64 Board due to system memory constraints.
** Rootable build, online update (OTA) only work when the build still not root.
** Set default HDMI output to 720P, video setting supports both 720P and 1080P
** Set default HDMI output to 720P, video setting supports both 720P and 1080P
** Add Ethernet Network setting.
** This build optimizes Gigabit Ethernet parameter and improves on GbE connectivity
** Update GMS software package to 5.1r4
** Update GMS software package to 5.1r4
** Set UVC USB camera as front camera and 5M Pixel camera module as real camera
** Set UVC USB camera as front camera and 5M Pixel camera module as real camera
** DD images:
 
*** For 8GB microSD Card
** DD image (for 8GB microSD Card):
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-8GB.zip Direct download from pine64.org]
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-8GB.img.gz Direct download from pine64.org]
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-8GB.zip.torrent Torrent Download]
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-8GB.img.gz.torrent Torrent Download]
**** MD5 (Zip file): 974C60C618A2F65657DDE9B1798812AB
*** MD5 (Zip file): 10FE76153EA1BAC8CB5E32D861728378
**** File Size: 646MB
*** File Size: 707MB
*** For 16GB microSD Card
 
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-16GB.zip Direct download from pine64.org]
** DD image (for 16GB microSD Card):
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-16GB.zip.torrent Torrent Download]
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-16GB.img.gz Direct download from pine64.org]
**** MD5 (Zip file): FAA48E4261451C1F54094AB6C253E76C
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-16GB.img.gz.torrent Torrent Download]
**** File Size: 655MB
*** MD5 (Zip file): 89F58F3E73D49C8C0457680EFB6964B3
*** For 32GB microSD Card
*** File Size: 773MB
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-32GB.zip Direct download from pine64.org]
 
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-32GB.zip.torrent Torrent Download]
** DD image (for 32GB microSD Card):
**** MD5 (Zip file): D46671B0FCE1B3572103E2615A494C78
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-32GB.img.gz Direct download from pine64.org]
**** File Size: 682MB
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-32GB.img.gz.torrent Torrent Download]
*** For 64GB microSD Card
*** MD5 (Zip file): 9656755D826164FA32FF95CF3B7D5B3A
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-64GB.zip Direct download from pine64.org]
*** File Size: 796MB
**** [http://files.pine64.org/os/android/android-ver5.1.1-20160711-pine64-64GB.zip.torrent Torrent Download]
 
**** MD5 (Zip file): C7453B4E84B145ED46FA927702FB97A3 
** DD image (for 64GB microSD Card):
**** File Size: 707MB
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-64GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/android/android-ver6.0-20170112-pine64-64GB.img.gz.torrent Torrent Download]
*** MD5 (Zip file): C89596F8B5A265BFEE567F8EC899697E 
*** File Size: 755MB
 
* '''Android 6.0.1 Image (LCD and HDMI Video Output) Release 20170209 [ver 2.0.1]'''
[[File:Logo_android_marshmallow.jpg]]
** The Android build is suitable for 1GB/2GB Pine A64+ Board but not advised to run on a 512MB Pine A64 Board due to system memory constraints.
** Support dual display (LCD + HDMI output) output.
** Set default HDMI output to 720P, video setting supports both 720P and 1080P
** LCD resolution is 1024 x 600, HDMI resolution is 1024 x 600 scale up to either 1280 x 720 pr 1920 x 1080
** Update GMS software package to 5.1r4
** Set UVC USB camera as front camera and 5M Pixel camera module as real camera
 
** DD image (for 8GB microSD Card):
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-8GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-8GB.img.gz.torrent Torrent Download]
*** MD5 (Zip file): 61E969F159C6B11D0632C6633C6A5583 
*** File Size: 761MB
 
** DD image (for 16GB microSD Card):
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-16GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-16GB.img.gz.torrent Torrent Download]
*** MD5 (Zip file): 0D83B4E698FEE88BAFF17606F4FB66C8
*** File Size: 777MB
 
** DD image (for 32GB microSD Card):
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-32GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-32GB.img.gz.torrent Torrent Download]
*** MD5 (Zip file): DFC12CA8342FBE1E604B85B4E83C49B2
*** File Size: 703MB
 
** DD image (for 64GB microSD Card):
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-64GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/android/android-ver6.0.1-lcd-version-20170209-pine64-64GB.img.gz.torrent Torrent Download]
*** MD5 (Zip file): 60E9ED3D93D37A15D29A0C5A3B4F2C52
*** File Size: 830MB
 


=== Remix OS 2.0 ===
=== Remix OS 2.0 ===
 
* '''Remix OS 2.0 Image Release 20170105'''
*'''Remix OS 2.0 Image Release 20160718'''
[[File:Logo_remix.jpg]]
[[File:Logo_remix.jpg]]
** Suitable for 2GB Pine A64+ Board, can runs on 1GB Pine A64+ Board with performance lagging, not suitable for 512MB Pine A64 Board
** Suitable for 2GB Pine A64+ Board, can runs on 1GB Pine A64+ Board with performance lagging, not suitable for 512MB Pine A64 Board
** This build optimizes Gigabit Ethernet parameter and improves on GbE connectivity.
** Add Remix apps market
** Add Remix apps market
** Video setting supports both 720P and 1080P
** Video setting supports both 720P and 1080P
Line 243: Line 371:
*** Even the HDMI output can set to 720P, but during boot up time, the boot logo stil maintain as 1080P.
*** Even the HDMI output can set to 720P, but during boot up time, the boot logo stil maintain as 1080P.
** DD image (for 8GB microSD Card):
** DD image (for 8GB microSD Card):
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-8GB.zip Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-8GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-8GB.zip.torrent Torrent download]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-8GB.img.gz.torrent Torrent download]
*** MD5 (Zip file): AE2256F46FAB2C9F8B9556FCB5995B3B
*** MD5 (Zip file): 77E499DF8BFF9A39F9C58E04877A41B5
*** File Size: 997MB
*** File Size: 1.10GB


** DD image (for 16GB microSD Card):
** DD image (for 16GB microSD Card):
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-16GB.zip Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-16GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-16GB.zip.torrent Torrent download]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-16GB.img.gz.torrent Torrent download]
*** MD5 (Zip file): 71587B7F7D86F39CD0874800C0491EA0
*** MD5 (Zip file): CF65049DA13A4AD8BA6D4BC19D97FB35
*** File Size: 1.02GB
*** File Size: 999MB


** DD image (for 32GB microSD Card):
** DD image (for 32GB microSD Card):
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-32GB.zip Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-32GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-32GB.zip.torrent Torrent download]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-32GB.img.gz.torrent Torrent download]
*** MD5 (Zip file): 0DAEC86248A7448B8D4F41B4DAEB9D6B
*** MD5 (Zip file): E1CA0D611307B5657BBFD73E4825C83D
*** File Size: 1.05GB
*** File Size: 1.18GB


** DD image (for 64GB microSD Card):
** DD image (for 64GB microSD Card):
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-64GB.zip Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-64GB.img.gz Direct download from pine64.org]
*** [http://files.pine64.org/os/remix/remix-v2.0-20160718-pine64-64GB.zip.torrent Torrent download]
*** [http://files.pine64.org/os/remix/remix-v2.0-20170105-pine64-64GB.img.gz.torrent Torrent download]
*** MD5 (Zip file): 6578237CB249DDE5A86A6D06D6793804
*** MD5 (Zip file): D6988832DDB5790EA2FC4DEE3CB6CCD9
*** File Size: 1.08GB
*** File Size: 1.18GB
 
 


== [http://wiki.pine64.org/index.php/Pine_A64_Software_Release Software and OS Image Downloads] ==
== [http://wiki.pine64.org/index.php/Pine_A64_Software_Release Software and OS Image Downloads] ==
Under [http://wiki.pine64.org/index.php/Pine_A64_Software_Release 'Pine A64 Software and OS Image Download Section'] you can find a complete list of currently supported Operating System images that work with the Pine A64 as well as other related software. The list includes OS images and descriptions of:
Under the [http://wiki.pine64.org/index.php/Pine_A64_Software_Release 'Pine A64 Software and OS Image Download Section'] you can find a complete list of currently supported Operating System images that work with the Pine A64 as well as other related software. The list includes OS images and descriptions of:
*Debian Jessie
* Debian Jessie
*Arch Linux  
* Arch Linux  
*Ubuntu 16.04
* Ubuntu 16.04
*Remix OS
* Remix OS
*Android 5.1
* Android 5.1
*Android 7.0  
* Android 6.0
*Windows IoT
* Android 7.0  
*OpenHAB  
* Windows IoT
* OpenHAB  
Provided are also H2testw 1.4 and F3 utilities used for checking microSD card performance, Allwinner's Phoenix Card bootable OS utility and other useful software.
Provided are also H2testw 1.4 and F3 utilities used for checking microSD card performance, Allwinner's Phoenix Card bootable OS utility and other useful software.
[http://wiki.pine64.org/index.php/Pine_A64_Software_Release Pine A64 Software and OS Image Download Section]


== [http://wiki.pine64.org/index.php/Accessories_Step_by_Step_Guides Accessories Step by Step Guides]==


== [http://wiki.pine64.org/index.php/Accessories_Step_by_Step_Guides Accessories Step-by-Step Guides] ==
Under [http://wiki.pine64.org/index.php/Accessories_Step_by_Step_Guides 'Guides for Pine A64 accessories'] you can find instructions and guides pertaining to:
Under [http://wiki.pine64.org/index.php/Accessories_Step_by_Step_Guides 'Guides for Pine A64 accessories'] you can find instructions and guides pertaining to:
*Enclosures
* Enclosures
*Bluetooth and WiFi module
* Bluetooth and WiFi module
*Real Time Clock (RTC) battery  
* Real Time Clock (RTC) battery  
*Real Time Clock (RTC) battery holder  
* Real Time Clock (RTC) battery holder  
*First and third party cases
* First and third party cases
*Featured 3D printed cases (and more).
* Featured 3D printed cases (and more).


== SoC and Memory Specification==
 
 
== SoC and Memory Specification ==
* Based on Allwinner A64  
* Based on Allwinner A64  
[[File:Allwinner_A64.jpg]]
[[File:Allwinner_A64.jpg]]
Line 308: Line 441:


=== System Memory ===
=== System Memory ===
* Main Memory Option: 512KB, 1GB and 2GB.
* RAM Memory Variants: 512MB, 1GB and 2GB.
* Storage Memory: No build in Flash memory, fully base on bootable microSD Card or USB attached storage.
* Storage Memory: Pine A64 boards ''do not'' have built-in Flash memory but use '''bootable microSD Cards''' or USB attached storage.
 
 


== Board Features ==
== Board Features ==
Line 338: Line 473:
* 2x5 pins "EXP" Console Header
* 2x5 pins "EXP" Console Header


== Power Usage ==
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, microUSB connector, Euler connector
* [http://wiki.pine64.org/images/1/1d/Power_Consumption.jpg Power Consumption: 2.5W]




 
== Pine A64 Board Information and Schematics ==
== Pine A64 Board information ==
* Board Dimensions: 133mm x 80mm x 19mm
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, microUSB connector, Euler connector
* [http://wiki.pine64.org/images/1/1d/Power_Consumption.jpg Power Consumption: 2.5W]
* [http://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png Pine A64 Connector Layout @courtesy of norm24]
* [http://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png Pine A64 Connector Layout @courtesy of norm24]
* [http://wiki.pine64.org/images/2/2e/Pine64_Board_Connector_heatsink.png Pine A64 Heat Sink Location @courtesy of norm24]
* [http://wiki.pine64.org/images/2/2e/Pine64_Board_Connector_heatsink.png Pine A64 Heat Sink Location @courtesy of norm24]
Line 357: Line 490:
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64plus%202GB%20Rev%20C-20160113_Release.pdf Pine A64+ 2GB Rev C Board Schematic]
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64plus%202GB%20Rev%20C-20160113_Release.pdf Pine A64+ 2GB Rev C Board Schematic]


== Datasheets ==
 
 
== Datasheets for Components and Peripherals ==
* Allwinner A64 SoC information:
* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
Line 389: Line 524:
** [http://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
** [http://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
** [http://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]
** [http://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]
*Remote control button mapping
* Remote control button mapping
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the Pine A64 Button Mapping]
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the Pine A64 Button Mapping]
* LCD Panel [Pinebook]
** [http://files.pine64.org/doc/pinebook/11.6inches-TFT-LCD%20Approval%20Specification%20N116BGE-E42%20Ver%203.0.pdf 11.6" LCD Panel datasheet]
** [http://files.pine64.org/doc/pinebook/14inches-HB140WX1-501(%20EDP1.2)%20Preliminary%20Product%20specification.pdf Official 14" LCD Panel datasheet]
* RGB to eDP LCD video signal translator [Pinebook]
** [http://files.pine64.org/doc/pinebook/ANX9807_Product_Brief.pdf ANX9807 Product Brief]
* Camera sensor [Pinebook]
** [http://files.pine64.org/doc/pinebook/ZC-RZ3762-3703-Camera-Module%20spec.pdf VGA Camera module specification]
** [http://files.pine64.org/doc/pinebook/VGA-CMOS-Sensor--BF3703%20Datasheet.pdf VGA Camera Sensor Data Sheet]


== Pine A64 POT ==
== Pine A64 POT ==
* [http://wiki.pine64.org/index.php/POT Pine A64 Peripheral On Top (POT) and Related Devices]
* [http://wiki.pine64.org/index.php/POT Pine A64 Peripheral On Top (POT) and Related Devices]
* [http://wiki.pine64.org/index.php/Wifi_Remote_I2c WiFi Remote I2c Quick Start Guide]
* [http://wiki.pine64.org/index.php/Wifi_Remote_I2c WiFi Remote I2c Quick Start Guide]


== Other Resources ==
== Other Resources ==

Revision as of 09:57, 5 April 2017

What You’ll Need to Get Started

You will need the following to get started with using your Pine A64 or A64+ board:

  • Windows / Linux PC or MAC with a SD Card Reader connected to the Internet
  • Power Supply (PSU) and a micro usb cable. Please make sure to use a PSU rated at +5V @2A and a micro USB cable that is at least 26 AWG thick.
  • MicroSD card (8GB or higher capacity) rated 'class 10' or better.
  • HDMI cable (unless you wish to run headless / without a monitor). N.B. Android and Remix OS support 720p and 1080p, while Linux supports a wider range of resolutions.
  • Input device(s) such as: keyboard, mouse, remote, pointer, etc.


Step by Step Instructions

Caution!

Please handle the Pine A64 or A64+ with care. Always hold the board by the edges and make sure to wear an anti-static wrist strap when handling the Pine A64 (+). Touching components on the front and back of the board can result in an ESD discharge that may damage your board. Avoid placing the board on materials such as carpets, plastics or other surfaces prone to electrostatic build-up.


Begin by imaging the OS of your choice

You will require a quality microSD card (8GB or greater; class 10 or faster). There are many substandard and counterfeit cards in circulation and even reputable vendors may unknowingly sell counterfeit microSD cards. Cards that do not meet the criteria outlined above are known to cause a variety of issues including, but not limited to, complete boot failure. There are ways of testing microSD cards prior to installing the operating system to make sure they are appropriate for use with your board. The main utility for checking microSD cards is H2testw 1.4; yet another alternative is F3.

Please refer to the relevant section below for instructions on how to image your microSD card:

Having successfully imaged your microSD card, insert it into the microSD slot located at the bottom left of the board / to the left of the USB 2.0 sockets.


Plug in the HDMI Cable, Ethernet Cable and Peripherals

Unless you are planning on running your Pine A64 (+) headless (without a monitor / as a server), you should plug in all necessary peripherals, including the HDMI and Ethernet cable, prior to powering ON the board. Do note, depending on which OS image you are using, some peripherals may or may not work. N.B. Some HDMI→DVI/VGA converters may not work in conjunction with your monitor or TV.


Apply Power to Your Board

Once you have imaged your microSD and plugged everything in, you are ready to apply power to the Pine A64(+) board. You'll need a good quality 5 Volt, 2 Amp PSU. Using a good quality PSU and micro USB cable is very important as failing to meet the required specifications may prevent the board from booting correctly. A marginally higher PSU Voltage is acceptable (for instance, 5.1 volts - due to the nature of the micro usb connection, a 5.1v supply can help protect slightly against voltage drops which can cause undesirable results). However, a significantly higher voltage of 7 Volts or more will damage the Pine A64(+) board and may render it inoperative.

If you are using a separate micro USB cable with your PSU, make sure that the cable has a low resistance rating. Cables with high resistance will cause improper function and the unit may not boot at all or only partially. The thicker the internal cabling, the better i.e. AWG (American Wire Gauge) 20 is better than AWG 28. In General, power-only microUSB cables come with red colour USB header.

Having completed the steps outlined above the Pine A64(+) board will begin to boot. The red onboard LED light indicates power on status. The LED will not blink during boot up and the colour of the LED stays solid. The colour does not change to signify an error.


Imaging microSD on Windows 7/8/8.1/10

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:

  • A compression Utility (used to unarchive the OS image). We recommend you use 7zip.
  • A disk image utility (used to ‘burn’ the .img to your SD card). We recommend you use either the Win32Imager or Etcher utility.

Optional

  • Phoenix Card image utility (used ONLY for phoenix card images). You can download it from here.


Downloading and extracting OS image(s)

You can find all curated OS images under Curated Pine A64 (A64+) OS Images. There are two type of Android and Remix images available. Images designated ‘DD’ need to be imaged using Etcher or Win32imager, whilst images labelled ‘Phoenix Card Image’ require the Phoenix Card utility.

Having downloaded the required OS image proceed to use 7zip to unarchive it by right-clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination of where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.


Imaging the microSD card (DD)

  • Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.
  • Launch Win32diskImager.exe or etcher.exe. You will be presented with a field titled ‘path’ and a drop down menu labeled ‘device’. Click the ‘path’, navigate to and select the OS image you extracted from the archive earlier. Next, from the drop-down menu select the drive your microSD has been assigned. N.B. Pay close attention to the selected drive (remember your letter) – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
  • Having chosen the desired OS image and the correct driver press ‘write’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from Windows.


Imaging using Phoenix Card

On Windows, you can also use Phoenix Card (for detailed instructions click here). The Phoenix Card utility works ONLY with images designated as ‘Phoenix Card’ in the downloads section. To use Phoenix Card follow these steps:

  • Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.
  • Launch phoenixcard.exe. You will be presented with a ‘disk’ drop-down menu and a field denoted as ‘Img File’. Click on ‘Img File’ and navigate to and select the OS image have downloaded and unarchived. Next, make sure to select the disk that your microSD card has been assigned. N.B. Pay close attention to the selected drive (remember your letter) – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
  • Make sure to select ‘Startup!’ from the ‘Write mode’ window and click Burn. Once the image has been written to your microSD card you will receive a confirmation in the ‘option’ window. Be sure to close the application and to eject/remove your SD card safely from Windows.



Imaging microSD on Apple OSX

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:

  • A compression Utility (used to unarchive the OS image). We recommend you use 7Zip.
  • A disk image utility (used to ‘burn’ the .img to your SD card in GUI). We recommend you use ApplePi Baker or Etcher.


N.B. Phoenix Card utility and images are NOT available on Apple OSX.


Downloading and extracting OS image(s)

You can find all curated OS images under Curated Pine A64 (A64+) OS Images. On OSX you can only use images designated as ‘DD’.

Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.


Imaging the microSD card (GUI)

  • Insert your microSD card into your Mac laptop/USB card reader. You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
  • Launch Apple-Pi Baker or the etcher utility. Upon startup the application it will ask for your password. When the application launches you will be presented with a field titled ‘IMG file’ and a path of the mounted microSD card (it will look something like this: ‘/dev/diskX 32.0Gb SD card’). Click the ‘IMG file’ button, navigate to and select the OS image you extracted from the archive earlier. Next, select the microSD from the window. N.B. Pay close attention to the selected drive – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
  • Having chosen the desired OS image and the correct driver press ‘Restore Backup’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your Mac.


Imaging from Terminal

N.B. If you are not comfortable using the terminal, please use the GUI method outlined above instead.

  • Insert your microSD card into your Mac laptop/USB card reader. You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
  • Open up your terminal and navigate to the directory where you unarchived your OS image.
  • Before you start writing to the card, you will have to identify your microSD card. Type: diskutil list and note the output. The disk number should match the size of your SD card and will likely be using ‘Fdisk_partition_scheme’. Having identified the disk number execute the following commands (substitute diskX for your disk and name of image for pine64-image-name.img):

diskutil unmountDisk /dev/diskX sudo dd if=pine64-image-name.img of=/dev/disk2 bs=1M

  • Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your Mac.



Imaging microSD on Linux

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:

  • A compression Utility (used to unarchive the OS image). We recommend you use 7Zip.
  • A disk image utility (used to ‘burn’ the .img to your SD card in GUI). We recommend you use Etcher or the GUI Disks utility that ships with most popular distros.


N.B. Phoenix Card utility and images are NOT available on Linux.


Downloading and extracting OS image(s)

You can find all curated OS images under Curated Pine A64 (A64+) OS Images. On Linux you can only use images designated as ‘DD’.

Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.


Imaging the microSD card (GUI)

  • Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in your File Manager / on your desktop.
  • Launch Disks or the etcher utility (This tutorial outlines how to use Disks, if you wish to learn how to use Etcher please visit their website).
  • Upon launching Disks, you will be presented with all volumes visible to your computer. As a rule of thumb, your microSD card should be found at the bottom of listed volumes. Verify this by checking the size and mounting of the microSD card. N.B. Pay close attention to the selected drive – the imaging process will format the selected drive. If you choose the wrong drive all your data will be lost.
  • Having selected your microSD card, click the cog menu in top right corner and choose the ‘Restore Disk Image’ option from the drop-down list. Navigate to and select the OS image you extracted from the archive earlier. Once you select it, you will be asked to enter your password and to confirm writing to the chosen volume (microSD card).
  • You will be given a predicted time, writing-speed and completion percentage. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your computer.


Imaging from Terminal

N.B. If you are not comfortable using the terminal, please use the GUI method outlined above instead.

  • Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
  • Open up your terminal and navigate to the directory where you unarchived your OS image.
  • Before you start writing to the card, you will have to identify your microSD card.
  • Type: lsblk and pay attention to the listed disks. Disks will appear as /dev/sda /dev/sdb etc. Look at the drive that matches your microSD card’s size.
  • Having located the microSD card use the following command to burn the .img of choice to the microSD card (/dev/sdb used as example): ‘’sudo unmount /dev/sdb1
  • Now you are ready to write the image to the microSD card using this command: ‘’sudo dd if=pine64_image_name.img of=/dev/sdb bs=1M
  • Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your computer.


Troubleshooting

There is a number of things that can prevent the Pine A64(+) board from booting up properly. The most common culprits of a failed boot are (to find out more click here):

  • Subpar or counterfeit microSD card
  • Subpar Power Supply
  • High resistance (thin) or a very long microUSB cable
  • Failed imaging of the microSD card (refer to the respective ‘imaging microSD card section)

Make sure to have the newest version of the OS image your are running. On Linux, you can update the kernel and uboot using scripts located in the following directory: /usr/local/sbin

  • To navigate to the directory type (in terminal): cd /usr/local/sbin
  • You list all the available scripts by typing (in terminal): ls
  • To run the script required update script run the following command: sudo ./update_script.sh (substitute the relevant update script for update_script)


Supported Screen Resolutions

The pine supports a number of video resolutions under Linux, however RemixOS and Android images currently only support 720p and 1080p. Linux supports a wider range of resolutions (see all resolutions supported on Linux here). If the native resolution of your monitor or TV is not compatible with the Pine A64(+) then you will be unable to get a video to work with your screen.


Troubleshooting Step by Step

Follow these steps to determine the cause of your problem:

  • Check your PSU and microUSB cable ratings
  • Download and image a base image of Linux
  • Plug in Power and Ethernet into your Board
  • Watch Ethernet port LED activity
  • Check your router for Pine A64(+) IP
  • Attempt to ssh into the Pine A64(+) from your computer

If your PSU and microUSB meet the criteria, and you have correctly followed the instructions to image your card and power on the board, but you are not seeing any LED activity and cannot ssh into your Pine A64(+) then either the imaging process failed (possibly due to a subpar microSD) OR the PSU / microUSB cable is/are faulty.

If your PSU and microUSB meet the criteria, and you have correctly imaged the OS to your card and power on the board and your can ssh into your Pine A64(+) but get no video feed, then it's likely that the native resolution of your monitor/TV is not supported.

If neither of the above mentioned scenarios fits the problem you are facing, please consult this thread (thanks to Ghost for compiling the list): http://forum.pine64.org/showthread.php?tid=680

If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/


Curated Sopine OS Images

Ubuntu

  • Ubuntu Desktop Image [20170306] built by Pine64

File:Logo ubuntu.jpg

    • This is a build including DE based on longsleep works and may not have all the up-to-date features offered by longsleep and Sunxi community. For latest build, you can create one and following this thread
    • This build optimizes Gigabit Ethernet parameter and improves on GbE connectivity.
    • Included Mate Desktop, Firebox Browser, and LibreOffice Suite.
    • Included libvdpau-sunxi with SMPlayer
    • Included with Wifi and Bluetooth
    • Included library set that provides access to the GPIO headers in Linux as provided by community member KB3VGW (https://devhub.io/repos/kb3vgw-wiringPi-Pine64)
    • Not yet optimize for Graphic acceleration
    • Suitable for Sopine Board only
  • Login with
    • username: ubuntu
    • password: ubuntu
  • Auto execute resize_rootfs.sh script on first boot-up to resize the root partition in order to fully utilize the SD Card
  • DD image (for 8GB micoSD card and above):

Android

  • DD image (for microSD Card to eMMC)
      • Burn this image to a 8GB microSD Card, insert into SOPINE and it will start program to eMMC. The power LED will be turn off when the process is completed. Unplug the MicroSD card from SOPINE to boot from eMMC.
      • Direct download from pine64.org
      • MD5 (Zip file): 99736D857E675254D4C3ACA95024B3F3
      • File Size: 673MB
  • Android 5.1.1 Image [20160630]
  • DD image (for 8GB microSD Card)

Curated Pine A64 (A64+) OS Images

Debian Jessie

  • Debian Jessie Linux by Lenny Raposo (Longsleep kernel 3.10.102 BSP 2)

File:Logo debian.jpg


Ubuntu 16.04

  • Ubuntu Linux Image by Longsleep (3.10.xxx)

File:Logo ubuntu.jpg

    • Thanks to longsleep's work, the Linux build progress rapidly. For latest build please see this thread
    • Suitable for 1GB/2GB Pine A64+ Board, not suitable for 512MB Pine A64 Board due to system memory constrain
    • DD image (for 8GB and above SD Card):
    • To install Mate desktop run: sudo /usr/local/sbin/install_mate_desktop.sh
    • Login with
      • username: ubuntu
      • password: ubuntu
    • Execute resize_rootfs.sh script to resize the root partition in order to fully utilize the SD Card


Android 6.0

  • Android 6.0 Image (HDMI Video Output) Release 20170112 [ver 2.0.1]

File:Logo android marshmallow.jpg

    • The Android build is suitable for 1GB/2GB Pine A64+ Board but not advised to run on a 512MB Pine A64 Board due to system memory constraints.
    • Set default HDMI output to 720P, video setting supports both 720P and 1080P
    • This build optimizes Gigabit Ethernet parameter and improves on GbE connectivity
    • Update GMS software package to 5.1r4
    • Set UVC USB camera as front camera and 5M Pixel camera module as real camera
  • Android 6.0.1 Image (LCD and HDMI Video Output) Release 20170209 [ver 2.0.1]

File:Logo android marshmallow.jpg

    • The Android build is suitable for 1GB/2GB Pine A64+ Board but not advised to run on a 512MB Pine A64 Board due to system memory constraints.
    • Support dual display (LCD + HDMI output) output.
    • Set default HDMI output to 720P, video setting supports both 720P and 1080P
    • LCD resolution is 1024 x 600, HDMI resolution is 1024 x 600 scale up to either 1280 x 720 pr 1920 x 1080
    • Update GMS software package to 5.1r4
    • Set UVC USB camera as front camera and 5M Pixel camera module as real camera


Remix OS 2.0

  • Remix OS 2.0 Image Release 20170105

Logo remix.jpg

    • Suitable for 2GB Pine A64+ Board, can runs on 1GB Pine A64+ Board with performance lagging, not suitable for 512MB Pine A64 Board
    • This build optimizes Gigabit Ethernet parameter and improves on GbE connectivity.
    • Add Remix apps market
    • Video setting supports both 720P and 1080P
    • Supports video screen scaling function
    • New MAC address assignment method, tags to board and SoC unique ID.
    • Support UVC USB camera as front camera
    • Known issues:
      • Not yet support 5M Pixel camera module as real camera
      • Even the HDMI output can set to 720P, but during boot up time, the boot logo stil maintain as 1080P.
    • DD image (for 8GB microSD Card):


Software and OS Image Downloads

Under the 'Pine A64 Software and OS Image Download Section' you can find a complete list of currently supported Operating System images that work with the Pine A64 as well as other related software. The list includes OS images and descriptions of:

  • Debian Jessie
  • Arch Linux
  • Ubuntu 16.04
  • Remix OS
  • Android 5.1
  • Android 6.0
  • Android 7.0
  • Windows IoT
  • OpenHAB

Provided are also H2testw 1.4 and F3 utilities used for checking microSD card performance, Allwinner's Phoenix Card bootable OS utility and other useful software.


Accessories Step-by-Step Guides

Under 'Guides for Pine A64 accessories' you can find instructions and guides pertaining to:

  • Enclosures
  • Bluetooth and WiFi module
  • Real Time Clock (RTC) battery
  • Real Time Clock (RTC) battery holder
  • First and third party cases
  • Featured 3D printed cases (and more).


SoC and Memory Specification

  • Based on Allwinner A64

Allwinner A64.jpg

CPU Architecture

  • Quad-core ARM Cortex-A53 Processor@1152Mhz
  • A power-efficient ARM v8 architecture
  • 64 and 32bit execution states for scalable high performance
  • Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
  • Support Large Physical Address Extensions(LPAE)
  • VFPv4 Floating Point Unit
  • 32KB L1 Instruction cache and 32KB L1 Data cache
  • 512KB L2 cache

GPU Architecture

System Memory

  • RAM Memory Variants: 512MB, 1GB and 2GB.
  • Storage Memory: Pine A64 boards do not have built-in Flash memory but use bootable microSD Cards or USB attached storage.


Board Features

Video

  • HDMI 1.4a (Type A - full)

Audio

  • 3.5mm stereo earphone/microphone plug

Network

  • 10/100/1000Mbps Ethernet(Pine A64+ version), 10/100Mbps Ethernet(Pine A64 version)
  • WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

Storage

  • microSD - bootable, support SDHC and SDXC, storage up to 256GB
  • USB - 2 USB2.0 Host port

Expansion Ports

  • DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
  • CSI - CMOS Camera Interface up to 5 mega pixel
  • TP - Touch Panel Port, SPI with interrupt
  • RTC - Real Time Clock Battery Connector
  • VBAT - Lithium Battery Connector with temperature sensor input
  • Wifi/BT Module Header - SDIO 3.0 and UART
  • 2x20 pins "Pi2" GPIO Header
  • 2x17 pins "Euler" GPIO Header
  • 2x5 pins "EXP" Console Header


Pine A64 Board Information and Schematics


Datasheets for Components and Peripherals


Pine A64 POT


Other Resources