Difference between revisions of "Main Page"

From PINE64
Jump to navigation Jump to search
m (Changed protection settings for "Main Page": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
 
(399 intermediate revisions by 43 users not shown)
Line 1: Line 1:
PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.


PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.


For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [[PINE64 brand and logo|article about our brand and logo]].


== Please Select Product Main page ==
== Devices ==


PINE A64, A64+, A64-LTS and SOPine under PINE A64 Main Page:
[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]


[{{fullurl:PINE A64}} http://files.pine64.org/wiki/PINE%20A64-LTS.png] [[PINE A64 Main Page]]           [{{fullurl:ROCK64}} http://files.pine64.org/wiki/Pinebook.png] [[Pinebook Main Page]]           [{{fullurl:ROCK64}} http://files.pine64.org/wiki/ROCK64.png] [[ROCK64 Main Page]]
You can learn more about the following devices manufactured by PINE64:


== What You’ll Need to Get Started ==
* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Phone accessories: '''[[PinePhone (Pro) Add-ons]]''' and '''[[PinePhone (Pro) Keyboard]]'''
* Tablets: '''[[PineTab]]''', '''[[PineTab2]]''', '''[[PineTab-V]]''' and '''[[PineNote]]'''
* Wearable: '''[[PineBuds Pro]]''', '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''' and '''[[Pinebook Pro]]'''
* Laptop accessories: '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Oz64]]''','''[[Ox64]]''', '''[[STAR64]]''', '''[[Quartz64]]''', '''[[QuartzPro64_Development|QuartzPro64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS]]''', '''[[PINE H64 Model A]]''' and '''[[PINE H64|PINE H64 Model B]]'''
* Set-top box: '''[[RockBox]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPINE]]''', '''[[SOPINE Baseboard]]''', '''[[SOEDGE]]''', '''[[SOEDGE Baseboard]]''', and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Power adapter: '''[[PinePower]]'''
* Soldering iron: '''[[Pinecil]]'''
* Makerspace: '''[[PineCone]]''' and '''[[Pinedio]]'''


You will need the following to get started with using your PINE A64 or A64+ board:
== Community and Support ==
* 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.


Community collaboration and support is focused around the chat platforms and forums described below. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.


=== Chat Platforms ===


== Simple Step to Image Your MicroSD ==
PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.
Please try our [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md 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.
{{hint|PINE64 community is not some always-responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently.  More precisely:
* The activity of community members varies depending on the time of day and the number of active users.
* Whether your questions will be answered and whether the answers are right and definitive, depends on the information you provide, the difficulty of your questions, the current state of the involved PINE64 products and their software support, and the community members' ability.
* Read [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] to learn more.
* Please read [[PINE64 Community Rules and Code of Conduct]].


'''Note:'''
* PINE64 uses a bridge bot (''[https://github.com/42wim/matterbridge matterbridge]'' with some modifications) that allows Discord, IRC, Matrix, and Telegram users to see each other and participate together in the community chat.
* The bot name is "Pine64 Protocol Droid" or "P64ProtocolBot", depending on the chat platform, and if you see this, look in the message to see the actual author of the message.
* When the bot relays messages, it will show the chat platform the user is using by prefixing their nickname with "[D]" for Discord, "[I]" for IRC, "[M]" for Matrix, and "[T]" for Telegram.
}}


The community chat platforms are the following:


== Step by Step Instructions ==
* '''Discord''': Use this '''[https://discord.gg/pine64 invite link]'''. All PINE64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below.
* '''IRC''': The server is '''irc.pine64.org''', and the ports are '''6667''' (plain) and '''6697''' (TLS). Use <code>/LIST</code> command or the table below to see the full list of channels. This server experienced abuse by spam bots in early October 2023, which resulted in requiring registration and authentication with <code>NickServ</code> before users could join channels between October 3, 2023 and October 11, 2023. Using <code>NickServ</code> to join channels has become required again on October 23, 2023, due to the server experiencing repeated abuse by spam bots.
* '''Matrix and Telegram''': See the table below.


'''Caution!'''
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://matrix.to/#/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://matrix.to/#/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://matrix.to/#/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://matrix.to/#/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://matrix.to/#/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://matrix.to/#/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz-dev
|-
| Star64
| [https://matrix.to/#/#star64:matrix.org #star64:matrix.org]
| [https://t.me/star64_sbc @star64-sbc]
| Unavailable
|-
| Pinebook and Pinebook Pro
| [https://matrix.to/#/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://matrix.to/#/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://matrix.to/#/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://matrix.to/#/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://matrix.to/#/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://matrix.to/#/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| PineBuds Pro
| [https://matrix.to/#/#pinebuds:matrix.org #pinebuds:matrix.org]
| [https://t.me/+nJVhM0mZ9KhlYmZl @pinebuds]
| Unavailable
|-
| Pinecil
| [https://matrix.to/#/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinecil Development
| [https://matrix.to/#/#pinecil-dev:matrix.org #pinecil-dev:matrix.org]
| [https://t.me/+8_pdKqXrVuQ4OTk1 Pinecil-dev]
| Unavailable
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| PineCube
| [https://matrix.to/#/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker, Ox64, Oz64
| [https://matrix.to/#/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://matrix.to/#/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://matrix.to/#/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #offtopic
|}


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.
There is also an unofficial Matrix Space at [https://matrix.to/#/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.


=== Forums ===


'''Begin by imaging the OS of your choice'''
PINE64 runs an official forum powered by the open-source forum server software ''MyBB''. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.


You will require a quality microSD card (8GB or greater; class 10 or faster). There are many [http://forum.pine64.org/showthread.php?tid=681 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  [http://www.softpedia.com/get/System/System-Miscellaneous/H2testw.shtml#download H2testw 1.4]; yet another alternative is [https://github.com/AltraMayor/f3/archive/v6.0.zip F3].
The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]


Please refer to the relevant section below for instructions on how to image your microSD card:
Also, these are the official Subreddits:
* [[#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 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.
* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]


== Helpful Information for Beginners ==


'''Plug in the HDMI Cable, Ethernet Cable and Peripherals'''
* '''[[Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
 
* '''[[How to Contribute]]''': Information about how to contribute to different partner projects
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.
* '''[[Where to Report Bugs]]''': Information about how to report bugs
 
* '''[[Project]]''': A variety of well documented PINE64 projects to serve as inspiration
 
'''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 [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.
 
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 [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.
'''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].
 
 
'''Downloading and extracting OS image(s)'''
 
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.
 
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 [[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.
 
* 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 [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].
 
 
'''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|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 [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 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.
 
 
'''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 ==
 
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 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 [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.
 
 
'''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/
 
 
 
 
 
== Other Resources ==
* [http://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]
* [https://github.com/umiddelb/z2d/tree/master/pine64 Collection of scripts to set up a minimal Xenial 14.04.3 / Debian 8 Jessie root filesystem Contributed By Uli Middelberg]
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]
* [http://blog.hypriot.com/post/the-pine-a64-is-about-to-become=the-cheapest-ARM-64-bit-platform-to-run-Docker/ PINE A64 with HypriotOS by Dieter and Govinda]
* [https://sosfakeflash.wordpress.com/2008/09/02/h2testw-14-gold-standard-in-detecting-usb-counterfeit-drives/comment-page-3/#comment-9861 H2testw 1.4 – Gold Standard In Detecting USB Counterfeit Drives]
* [http://oss.digirati.com.br/f3/ F3 - an alternative to h2testw]
* [http://www.phoronix.com/scan.php?page=article&item=pine-64-benchmark&num=1 Benchmarking The Low-Cost PINE 64+ ARM Single Board Computer by Michael Larabel]
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]
* [https://www.youtube.com/playlist?list=PLgj96wTPcMKffRm_Sk6673Nfy_I6b5UJW A series of Youtube video on PINE A64 Developers Board by Michael Larson]
* [http://rayhightower.com/blog/2016/04/04/pine64-quick-start-guide-using-mac-os-x/ PINE64 Quick Start Guide (with Gotchas)]
* [http://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]

Latest revision as of 12:50, 20 November 2024

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the PINE A64 single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see Community and Support for a list of available channels and chat platforms. To learn more about PINE64, please visit the PINE64 website and the PINE64 store.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the article about our brand and logo.

Devices

Pinebook Pro (left) and PinePhone (right)

You can learn more about the following devices manufactured by PINE64:

Community and Support

Community collaboration and support is focused around the chat platforms and forums described below. See Getting Started | PINE64 for tips about how to get started with the PINE64 community.

Chat Platforms

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

PINE64 community is not some always-responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently. More precisely:
  • The activity of community members varies depending on the time of day and the number of active users.
  • Whether your questions will be answered and whether the answers are right and definitive, depends on the information you provide, the difficulty of your questions, the current state of the involved PINE64 products and their software support, and the community members' ability.
  • Read How To Ask Questions The Smart Way to learn more.
  • Please read PINE64 Community Rules and Code of Conduct.

Note:

  • PINE64 uses a bridge bot (matterbridge with some modifications) that allows Discord, IRC, Matrix, and Telegram users to see each other and participate together in the community chat.
  • The bot name is "Pine64 Protocol Droid" or "P64ProtocolBot", depending on the chat platform, and if you see this, look in the message to see the actual author of the message.
  • When the bot relays messages, it will show the chat platform the user is using by prefixing their nickname with "[D]" for Discord, "[I]" for IRC, "[M]" for Matrix, and "[T]" for Telegram.

The community chat platforms are the following:

  • Discord: Use this invite link. All PINE64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below.
  • IRC: The server is irc.pine64.org, and the ports are 6667 (plain) and 6697 (TLS). Use /LIST command or the table below to see the full list of channels. This server experienced abuse by spam bots in early October 2023, which resulted in requiring registration and authentication with NickServ before users could join channels between October 3, 2023 and October 11, 2023. Using NickServ to join channels has become required again on October 23, 2023, due to the server experiencing repeated abuse by spam bots.
  • Matrix and Telegram: See the table below.
Channel Matrix Telegram IRC
PINE64 News #pine64-announcements:matrix.org @PINE64_News Unavailable
General PINE64 chat #pine64:matrix.org @mtrx_pine64 #pine64
PINE A64(+), A64-LTS & SOPine #pine64sopine:matrix.org @pine64sopine #lts-sopine
ROCK64 / ROCKPro64 #rock64:matrix.org @mtrx_rock64 #rock64
Quartz64 #quartz64:matrix.org Quartz64 #quartz64
Quartz64 Development #quartz64-dev:matrix.org @q64dev #quartz-dev
Star64 #star64:matrix.org @star64-sbc Unavailable
Pinebook and Pinebook Pro #pinebook:matrix.org @mtx_pinebook #pinebook
PinePhone #pinephone:matrix.org @pinephone #pinephone
PineNote #pinenote:matrix.org @PineNote #pinenote
PineTab #pinetab64:matrix.org @PineTab #pinetab
PineTime #pinetime:matrix.org @pinetime #pinetime
PineTime Development #pinetime-dev:matrix.org @pinetime_dev #pinetime-dev
PineBuds Pro #pinebuds:matrix.org @pinebuds Unavailable
Pinecil #pinecil:matrix.org Pinecil #pinecil
Pinecil Development #pinecil-dev:matrix.org Pinecil-dev Unavailable
Pinetalk Podcast Unavailable Unavailable Unavailable
PineCube #cube64:matrix.org @pinecube #cube
Nutcracker, Ox64, Oz64 #pine64-nutcracker:matrix.org Nutcracker #nutcracker
LoRa #pinelora:matrix.org @pine64lora #lora
Off-topic #offtopic64:matrix.org @pine64offtopic #offtopic

There is also an unofficial Matrix Space at #pine64-space:matrix.org for supported clients that organizes all of the above matrix channels into one place.

Forums

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:

Also, these are the official Subreddits:

Helpful Information for Beginners

  • Getting started: Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
  • How to Contribute: Information about how to contribute to different partner projects
  • Where to Report Bugs: Information about how to report bugs
  • Project: A variety of well documented PINE64 projects to serve as inspiration
Retrieved from "https://wiki.pine64.org/index.php?title=Main_Page&oldid=21676"