Difference between revisions of "Pine64"

From eLinux.org
Jump to: navigation, search
(Adding how to get a Serial console on PINE64 with TTL cable.)
(removing links to pine64.pro as they go to inappropriate page now)
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
== PINE 64 ==
 
== PINE 64 ==
  
[http://www.pine64.com Officiel Website]
+
[https://www.pine64.com Official Website]
  
 
=== Documentation ===
 
=== Documentation ===
 
+
NOTE: All links to the old pine64.pro page have been removed as they currently redirect to inappropriate material.
 +
<!--
 
[http://www.pine64.pro/download/documents/allwinner-a64-introduction.pdf AllWinner A64 Introduction]
 
[http://www.pine64.pro/download/documents/allwinner-a64-introduction.pdf AllWinner A64 Introduction]
 
<br/>[http://www.pine64.pro/download/documents/allwinner-a64-datasheet.pdf AllWinner A64 Datasheet]
 
<br/>[http://www.pine64.pro/download/documents/allwinner-a64-datasheet.pdf AllWinner A64 Datasheet]
Line 14: Line 15:
 
<br/>[http://www.pine64.pro/download/documents/pine64-layout-dimensions.pdf Layout & Dimensions]
 
<br/>[http://www.pine64.pro/download/documents/pine64-layout-dimensions.pdf Layout & Dimensions]
 
<br/>[http://www.pine64.pro/download/documents/pine64-schematics.pdf Schematics]
 
<br/>[http://www.pine64.pro/download/documents/pine64-schematics.pdf Schematics]
 +
-->
 +
 
=== Linux Images ===
 
=== Linux Images ===
  
Line 21: Line 24:
 
===== Writing the image =====
 
===== Writing the image =====
  
<syntaxhighlight lang="bash">$sudo dd if=Ubuntu\ Pine64\ ML-Linux.img of=/dev/<your sdcard></syntaxhighlight>
+
<syntaxhighlight lang="bash">
 +
$ sudo dd if=Ubuntu\ Pine64\ ML-Linux.img of=/dev/<your sdcard>
 +
</syntaxhighlight>
  
 
====== User Login ======
 
====== User Login ======
*User Name: Ubuntu Password: ubuntu
+
*User Name: Ubuntu Password: ubuntu
*User Name: Ubuntu2 Password: ubuntu2
+
*User Name: Ubuntu2 Password: ubuntu2
  
 
=== Debian Images ===
 
=== Debian Images ===
 +
<!--Debian Images for the Pine A64 & A64+ can be found at [https://www.pine64.pro/downloads/#Debian-Linux Pine64 Pro]-->
  
 
=== Android Images ===
 
=== Android Images ===
Line 33: Line 39:
 
=== Caveats ===
 
=== Caveats ===
  
* Do not use a DVI-HDMI adapter. If you want video output, use a HDMI cable direct to a HDMI monitor or TV. This may change as development continues.
+
* Do not use a DVI-HDMI adapter. If you want video output, use a HDMI cable direct to a HDMI monitor or TV. This may change as development continues.
  
* Get a USB power supply that is at least 5V/1.5A. An underpowered supply will not boot the board.
+
* Get a USB power supply that is at least 5V/1.5A. An underpowered supply will not boot the board.
  
 
=== Serial Console ===
 
=== Serial Console ===
  
This paragraph describes a successful connection providing a UART Serial Console on a Linux Host. The PINE64 board used is a 2GB version (A64-DB-2B-Rev 6). The connection is provided by a FTDI TTL-232R-RPi 3-wire cable purchased from Digikey:
+
This paragraph describes a successful connection providing a UART Serial Console on a Linux Host. The PINE64 board used is a 2GB version (A64-DB-2B-Rev 6). The connection is provided by a FTDI TTL-232R-RPi 3-wire cable purchased from Digikey:
  
 
* [http://www.digikey.com/product-search/en?keywords=TTL-232R-RPi FTDI TTL-232R-RPi]
 
* [http://www.digikey.com/product-search/en?keywords=TTL-232R-RPi FTDI TTL-232R-RPi]
Line 45: Line 51:
 
The successful connection is made on the EXP connector:
 
The successful connection is made on the EXP connector:
  
* Connect the Black GND wire to Pin 6 of the EXP connector.
+
* Connect the Black GND wire to Pin 6 or 9 of the EXP connector.
 
* Connect the Yellow RX wire to Pin 7 of the EXP connector.
 
* Connect the Yellow RX wire to Pin 7 of the EXP connector.
 
* Connect the Orange TX wire to Pin 8 of the EXP connector.
 
* Connect the Orange TX wire to Pin 8 of the EXP connector.
  
Plug the FTDI TTL-232R-RPi USB end into your Linux host. Note the power LED on the PINE64 will illuminate at about half intensity.  Now find the tty that has been assigned to the FTDI TTL-232R-RPi by opening a terminal window and typing $dmesg. The last group of messages will show you how Linux has mapped the FTDI TTL-232R-RPi to the tty. In my case the output appears as:
+
Plug the FTDI TTL-232R-RPi USB end into your Linux host. Find the tty that has been assigned to the FTDI TTL-232R-RPi by opening a terminal window and typing $dmesg. The last group of messages will show you how Linux has mapped the FTDI TTL-232R-RPi to the tty. In my case the output appears as:
  
 
<pre>
 
<pre>
Line 63: Line 69:
 
</pre>
 
</pre>
  
The final line of the output indicates the FTDI USB Serial Device has been assigned to ttyUSB0. Now open a screen session with:
+
The final line of the output indicates the FTDI USB Serial Device has been assigned to ttyUSB0. Now open a screen session with:
  
<pre>
+
<syntaxhighlight lang="bash">
$sudo screeen /dev/ttyUSB0 115200
+
$ sudo screeen /dev/ttyUSB0 115200
</pre>
+
</syntaxhighlight>
  
 
Boot the PINE64 and you should see output in the terminal window on your Linux host.
 
Boot the PINE64 and you should see output in the terminal window on your Linux host.
  
[[Category:PINE64]]
+
=== Cooling ===
 +
 
 +
If the pine64 isn't stable during heavy computing calculation (like compilation), you can try to cool it down with some cheap heatsinks. I found them on an online auction website for a few dollars.
 +
Here are the dimensions of mine :
 +
* Processor : 20×20 mm
 +
* Regulator : 9×9 mm
 +
* RAM : 14×14 mm
 +
 
 +
[[File:Heatsinks-for-pine64.png|center]]
 +
 
 +
Those heatsinks are shipped with a thermal pad which allows an easier attachment to the IC.
 +
 
 +
Here is the PINE64 with heatsinks mounted on it:
 +
 
 +
[[File:Pine64-heatsink.jpeg|thumbnail|center]]
 +
 
 +
The board doesn't hang anymore and the temperature is lowered of 10°C (50°F). As the processor is less hot, the frequency can be higher and stay more stable to around 820 MHz.
 +
 
 +
[http://www.monbook.tech/realisations_pine64_en.html More details about cooling the pine64]
 +
 
 +
[[category:SBC with Allwinner SoC]]
 +
[[category:SBC with ARM CPU]]

Revision as of 06:39, 17 May 2019

PINE 64

Official Website

Documentation

NOTE: All links to the old pine64.pro page have been removed as they currently redirect to inappropriate material.

Linux Images

Ubuntu Linux Image base on Longsleep 20160403-1 image, courtesy of Michael Larson

Writing the image
$ sudo dd if=Ubuntu\ Pine64\ ML-Linux.img of=/dev/<your sdcard>
User Login
  • User Name: Ubuntu Password: ubuntu
  • User Name: Ubuntu2 Password: ubuntu2

Debian Images

Android Images

Caveats

  • Do not use a DVI-HDMI adapter. If you want video output, use a HDMI cable direct to a HDMI monitor or TV. This may change as development continues.
  • Get a USB power supply that is at least 5V/1.5A. An underpowered supply will not boot the board.

Serial Console

This paragraph describes a successful connection providing a UART Serial Console on a Linux Host. The PINE64 board used is a 2GB version (A64-DB-2B-Rev 6). The connection is provided by a FTDI TTL-232R-RPi 3-wire cable purchased from Digikey:

The successful connection is made on the EXP connector:

  • Connect the Black GND wire to Pin 6 or 9 of the EXP connector.
  • Connect the Yellow RX wire to Pin 7 of the EXP connector.
  • Connect the Orange TX wire to Pin 8 of the EXP connector.

Plug the FTDI TTL-232R-RPi USB end into your Linux host. Find the tty that has been assigned to the FTDI TTL-232R-RPi by opening a terminal window and typing $dmesg. The last group of messages will show you how Linux has mapped the FTDI TTL-232R-RPi to the tty. In my case the output appears as:

[308564.376087] usb 3-1.1: new full-speed USB device number 10 using ehci-pci
[308564.474534] usb 3-1.1: New USB device found, idVendor=0403, idProduct=6001
[308564.474541] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[308564.474545] usb 3-1.1: Product: TTL232R-3V3
[308564.474548] usb 3-1.1: Manufacturer: FTDI
[308564.474551] usb 3-1.1: SerialNumber: FT99JN2P
[308564.476846] ftdi_sio 3-1.1:1.0: FTDI USB Serial Device converter detected
[308564.476906] usb 3-1.1: Detected FT232RL
[308564.477263] usb 3-1.1: FTDI USB Serial Device converter now attached to ttyUSB0

The final line of the output indicates the FTDI USB Serial Device has been assigned to ttyUSB0. Now open a screen session with:

$ sudo screeen /dev/ttyUSB0 115200

Boot the PINE64 and you should see output in the terminal window on your Linux host.

Cooling

If the pine64 isn't stable during heavy computing calculation (like compilation), you can try to cool it down with some cheap heatsinks. I found them on an online auction website for a few dollars. Here are the dimensions of mine :

  • Processor : 20×20 mm
  • Regulator : 9×9 mm
  • RAM : 14×14 mm
Heatsinks-for-pine64.png

Those heatsinks are shipped with a thermal pad which allows an easier attachment to the IC.

Here is the PINE64 with heatsinks mounted on it:

Pine64-heatsink.jpeg

The board doesn't hang anymore and the temperature is lowered of 10°C (50°F). As the processor is less hot, the frequency can be higher and stay more stable to around 820 MHz.

More details about cooling the pine64