Difference between revisions of "Main Page"
m |
|||
Line 64: | Line 64: | ||
'''Downloading and extracting OS image(s)''' | '''Downloading and extracting OS image(s)''' | ||
You can find all | You can find all OS images under [[#Software_and_OS_Image_Downloads|Software and OS Image Downloads]]. | ||
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. | ||
Line 103: | Line 103: | ||
'''Downloading and extracting OS image(s)''' | '''Downloading and extracting OS image(s)''' | ||
You can find all | You can find all OS images under [[#Software_and_OS_Image_Downloads|Software and OS Image Downloads]]. 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. | ||
Line 146: | Line 146: | ||
'''Downloading and extracting OS image(s)''' | '''Downloading and extracting OS image(s)''' | ||
You can find all | You can find all OS images under [[#Software_and_OS_Image_Downloads|Software and OS Image Downloads]]. 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. | 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. | ||
Line 170: | Line 170: | ||
* 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. | * 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. | * 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. | * 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. | * 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'' | * 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'' | * 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. | * Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your computer. | ||
Line 180: | Line 180: | ||
== 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) | ||
Line 201: | Line 201: | ||
'''Troubleshooting Step by Step''' | '''Troubleshooting Step by Step''' | ||
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 | ||
Line 212: | Line 212: | ||
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. | ||
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 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 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/ | ||
Line 476: | Line 258: | ||
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. | ||
---- | |||
=== [[SOPINE_Software_Release|SOPINE]] === | |||
Under the [[SOPINE_Software_Release|'SOPINE Software and OS Image Download Section']] you can find a complete list of currently supported Operating System images that work with the SOPINE as well as other related software. The list includes OS images and descriptions of: | |||
* [{{fullurl:SOPINE_Software_Release#Ubuntu_Mate}} http://files.pine64.org/sw/pine64_installer/json/ubuntu_mate.png] [[SOPINE_Software_Release#Ubuntu_Mate|'''Ubuntu Mate''']] | |||
* [{{fullurl:SOPINE_Software_Release#Android_6.x}} http://files.pine64.org/sw/pine64_installer/json/android_6.png] [[SOPINE_Software_Release#Android_6.x|'''Android 6.x''']] [{{fullurl:SOPINE_Software_Release#Android_5.x}} http://files.pine64.org/sw/pine64_installer/json/android.png] [[SOPINE_Software_Release#Android_5.x|'''Android 5.x''']] | |||
* [{{fullurl:SOPINE_Software_Release#openSUSE_Base_Image}} http://files.pine64.org/sw/pine64_installer/json/opensuse.png] [[SOPINE_Software_Release#openSUSE_Base_Image|'''openSUSE''']] | |||
Line 483: | Line 276: | ||
* 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). | ||
Line 491: | Line 284: | ||
== 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 500: | Line 293: | ||
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function | * Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function | ||
* Support Large Physical Address Extensions(LPAE) | * Support Large Physical Address Extensions(LPAE) | ||
* VFPv4 Floating Point Unit | * VFPv4 Floating Point Unit | ||
* 32KB L1 Instruction cache and 32KB L1 Data cache | * 32KB L1 Instruction cache and 32KB L1 Data cache | ||
* 512KB L2 cache | * 512KB L2 cache | ||
=== GPU Architecture === | === GPU Architecture === | ||
Line 524: | Line 317: | ||
=== Network === | === Network === | ||
* 10/100/1000Mbps Ethernet(Pine A64+ version), 10/100Mbps Ethernet(Pine A64 version) | * 10/100/1000Mbps Ethernet(Pine A64+ version), 10/100Mbps Ethernet(Pine A64 version) | ||
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional) | * WiFi 802.11 b/g/n with Bluetooth 4.0 (optional) | ||
=== Storage === | === Storage === | ||
Line 536: | Line 329: | ||
* RTC - Real Time Clock Battery Connector | * RTC - Real Time Clock Battery Connector | ||
* VBAT - Lithium Battery Connector with temperature sensor input | * VBAT - Lithium Battery Connector with temperature sensor input | ||
* Wifi/BT Module Header - SDIO 3.0 and UART | * Wifi/BT Module Header - SDIO 3.0 and UART | ||
* 2x20 pins "Pi2" GPIO Header | * 2x20 pins "Pi2" GPIO Header | ||
* 2x17 pins "Euler" GPIO Header | * 2x17 pins "Euler" GPIO Header | ||
Line 568: | Line 361: | ||
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet] | ** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet] | ||
* '''PINE A64, PINE A64+ and SOPINE Related:''' | * '''PINE A64, PINE A64+ and SOPINE Related:''' | ||
** 5MPixel CMOS Camera module information: | ** 5MPixel CMOS Camera module information: | ||
*** [http://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf Pine64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)] | *** [http://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf Pine64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)] | ||
*** [http://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet] | *** [http://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet] |
Revision as of 16:22, 11 May 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.
Simple Step to Image Your MicroSD
Please try our PINE64 Installer to easily select the PINE A64(+), SOPINE and Pinebook OS of your choice and flash it to your MicroSD Card.
For more advance steps, you can further read instructions below.
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 OS images under Software and OS Image Downloads. 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 OS images under Software and OS Image Downloads. 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 OS images under Software and OS Image Downloads. 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/
Software and OS Image Downloads
PINE A64(+)
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:
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.
SOPINE
Under the 'SOPINE Software and OS Image Download Section' you can find a complete list of currently supported Operating System images that work with the SOPINE as well as other related software. The list includes OS images and descriptions of:
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
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
- ARM Mali400MP2 Dual-core GPU
- Support OpenGL ES 2.0 and OpenVG 1.1 standard
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
- Board Dimensions: 133mm x 80mm x 19mm
- Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, microUSB connector, Euler connector
- Power Consumption: 2.5W
- Pine A64 Connector Layout @courtesy of norm24
- Pine A64 Heat Sink Location @courtesy of norm24
- Pine A64 Connector List
- Pine A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)
- Pine A64 PCB dimension
- Board Model Comparison
- Pine A64 Board Schematic:
Datasheets for Components and Peripherals
- Allwinner A64 SoC information:
- X-Powers AXP803 PMU (Power Management Unit) information:
- PINE A64, PINE A64+ and SOPINE Related:
- 5MPixel CMOS Camera module information:
- LCD Touch Screen Panel information:
- Lithium Battery information:
- Ethernet PHY information:
- Wifi/BT module information:
- Enclosure information:
- Connector information:
- Remote control button mapping
- Pinebook Related:
- LCD Panel
- Touchpad information:
- Camera sensor
- Lithium Battery information:
Pine A64 POT
Other Resources
- Linux Sunxi Wiki page on Pine A64
- Collection of scripts to set up a minimal Ubuntu 14.04.3 / Debian 8 Jessie root filesystem Contributed By Uli Middelberg
- Linux Image created by Andre Przywara
- Pine A64 with HypriotOS by Dieter and Govinda
- H2testw 1.4 – Gold Standard In Detecting USB Counterfeit Drives
- F3 - an alternative to h2testw
- Benchmarking The Low-Cost PINE 64+ ARM Single Board Computer by Michael Larabel
- Pine64 Linux build scripts, tools and instructions by Longsleep
- Pine64 Linux image by Longsleep
- A series of Youtube video on PineA64 Developers Board by Michael Larson
- Pine64 Quick Start Guide (with Gotchas)
- Shrinking images on Linux by FrozenCow