Difference between revisions of "Pinebook"

From PINE64
Jump to navigation Jump to search
 
(101 intermediate revisions by 16 users not shown)
Line 1: Line 1:
[[File:PinebookMain.jpg|400px|thumb|right|The Pinebook]]


== What You’ll Need to Get Started ==
The '''Pinebook''' is an 11.6″ or 11.6″ with 1080P IPS panel or 14″ notebook powered by the same quad-core ARM Cortex A53 64-Bit Processor used in our popular PINE A64 Single Board Computer. It is very lightweight, hackable and comes equipped with a full-sized keyboard and large multi-touch trackpad. It runs numerous mainline Linux distributions as well as *BSD and Android.


You will need the following to get started with using your Pinebook:
== Software releases ==
* Windows / Linux PC or MAC with a SD Card Reader connected to the Internet.
* Power Supply (PSU). Please make sure to use a PSU rated at +5V @3A.
* MicroSD card (8GB or higher capacity) rated 'class 10' or better.
* Input device(s) such as: keyboard, mouse, remote, pointer, etc.


Under [[Pinebook Software Releases]] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.


== Variants ==


== Simple Step to Image Your MicroSD ==
The following variants exist of the Pinebook:
Please try our [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md PINE64 Installer] to easily select the Pinebook OS of your choice and flash it to your MicroSD Card.


For more advance steps, you can further read instructions below.
* Pinebook 11.6″
* Pinebook 11.6″ 1080p
* Pinebook 14″


More information can be found on the [https://linux-sunxi.org/Pine_Pinebook sunxi wiki].


== Pinebook Service Step-by-Step Guides ==
These are instruction guides for the disassembly:


== Step by Step Instructions ==
{{Info|The installation process is the reverse order of removal guide}}


'''Begin by imaging the OS of your choice'''
11.6″ Pinebook:
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-Battery_Removal_Guide.pdf Lithium Battery Pack Removal Guide]
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-Screen_Removal_Guide.pdf LCD Panel Screen Removal Guide]
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_11.6-eMMC_Removal_Guide.pdf eMMC Module Removal Guide]


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].
14″ Pinebook:
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Battery_Removal_Guide.pdf Lithium Battery Pack Removal Guide]
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Screen_Removal_Guide.pdf LCD Panel Screen Removal Guide]
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_14-eMMC_Removal_Guide.pdf eMMC Module Removal Removal Guide]


Please refer to the relevant section below for instructions on how to image your microSD card:
== Pinebook Information ==
* [[#Imaging microSD on Windows 7/8/8.1/10|Imaging microSD on Windows 7/8/8.1/10]]
* Dimensions: 299mm x 200mm x 12mm (WxDxH - 11″ Pinebook); 329mm x 220mm x 12mm (WxDxH - 14″ Pinebook)
* [[#Imaging microSD on Apple OSX|Imaging microSD on Apple OSX]]
* Weight: 1.04Kg (11″ Pinebook); 1.26Kg (14″ Pinebook)#
* [[#Imaging microSD on Linux|Imaging microSD on Linux]]
* Input Power: DC 5V @ 3A


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.
== SoC and Memory Specification ==
* Based on Allwinner A64
[[File:Allwinner_A64.jpg|right]]


CPU Architecture:
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php 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


'''Plug in the HDMI Cable, Ethernet Cable and Peripherals'''
GPU Architecture:
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]
* Support OpenGL ES 2.0 and OpenVG 1.1 standard
* [https://gitlab.freedesktop.org/lima/web/wikis/home Open source driver]


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.
System Memory:
* System RAM Memory: 2GB
* Storage Memory: 16GB eMMC module, can be upgrade to 32GB or 64GB eMMC module


Battery:
* Lithium Polymer Battery (10,000mAH)


'''Apply Power to Your Board'''
Video:
* Mini Digital Video Port (Type A - mini)


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.
Audio:
* 3.5mm stereo earphone/microphone plug


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.
Network:
* WiFi 802.11 b/g/n with Bluetooth 4.0
* 10/100Mbps USB Ethernet Dongle (Optional)


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.
Storage:
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port


Expansion Ports:
* mini Digital Video port
* microSD card port - support SD, SDHC, SDXC uo to 256GB
* 2x USB 2.0 port
* earphone plug with UART console mux circuit


== Pinebook Schematics and Certifications ==


=== Imaging microSD on Windows 7/8/8.1/10 ===
Mainboard schematics:
* [https://files.pine64.org/doc/pinebook/pinebook_mainboard_schematic_3.0.pdf Pinebook Mainboard schematics]


Daughter Board schematics:
* [https://files.pine64.org/doc/pinebook/pinebook_smallboard_schematic_1.0.pdf Pinebook Daughter board schematics]


You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
Serial Console Earphone Jack pinout:
* A compression Utility (used to unarchive the OS image). We recommend you use [http://www.7-zip.org/download.html 7zip].
* [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinebook Serial Console Earphone Jack pinout]
* 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].


Certifications:
* [https://files.pine64.org/doc/cert/Pinebook%20FCC%20certification%20VOC20170928.pdf Pinebook FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinebook%20FCC%20ID-Spread%20Spectrum%20Transmitter.pdf Pinebook FCC ID-Spread Spectrum Transmitter Certificate]
* [https://files.pine64.org/doc/cert/Pinebook%20FCC%20ID-Digital%20Transmission%20System.pdf Pinebook FCC ID-Digital Transmission System Certificate]
* [https://files.pine64.org/doc/cert/Pinebook%20CE%20certification%20Micom20171207.pdf Pinebook CE Certificate]
* [https://files.pine64.org/doc/cert/Pinebook%20ROHS%20certification%20VOC20170918.pdf Pinebook RoHS Certificate]


'''Downloading and extracting OS image(s)'''
== Datasheets for Components and Peripherals ==


You can find all OS images under [[#Software_and_OS_Image_Downloads|Software and OS Image Downloads]].
Allwinner A64 SoC:
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.
* [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
* [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
* [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]


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.
X-Powers AXP803 PMU (Power Management Unit):
* [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]


LPDDR3:
* [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]


'''Imaging the microSD card (DD)'''
eMMC:
* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]


* 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.
SPI NOR flash:
* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]


* 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.
WiFi/BT module:
* [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]


* 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.
LCD Panel:
* [https://files.pine64.org/doc/datasheet/pinebook/11.6inches-1080P-IPS-LCD-Panel-spec-WJFH116008A.pdf 1920x1080 1080P 11.6″ IPS LCD Panel datasheet]
* [https://files.pine64.org/doc/datasheet/pinebook/11.6inches-TFT-LCD%20Approval%20Specification%20N116BGE-E42%20Ver%203.0.pdf 1366x768 11.6″ TFT LCD Panel datasheet]
* [https://files.pine64.org/doc/datasheet/pinebook/14inches-HB140WX1-501(%20EDP1.2)%20Preliminary%20Product%20specification.pdf 1366x768 14″ TFT LCD Panel datasheet]


Touchpad:
* [https://files.pine64.org/doc/datasheet/pinebook/11-Toucpad-HK-9058%20specification.pdf Touchpad Specification for 11.6″ model]
* [https://files.pine64.org/doc/datasheet/pinebook/14-Touchpad-HK-9562%20specification.pdf Touchpad Specification for 14″ model]


'''Imaging using Phoenix Card'''
Camera sensor:
* [https://files.pine64.org/doc/datasheet/pinebook/ZC-RZ3762-3703%C2%A0S1.0-Camera-Module%20spec.pdf VGA Camera module specification]
* [https://files.pine64.org/doc/datasheet/pinebook/VGA-CMOS-Sensor--BF3703%20Datasheet.pdf VGA Camera Sensor Data Sheet]


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:
Lithium battery:
* [https://files.pine64.org/doc/datasheet/pinebook/PL5267103P-3.7V-10000mAh-1S2P58-9-W101-7P正向-11.6.pdf 10000mAH Lithium Battery Specification for 11.6″ model]
* [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14″ model]


* 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.
== Other Resources ==
 
* [https://linux-sunxi.org/Pine_Pinebook Linux Sunxi Wiki page on Pinebook]
* 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.
* [https://github.com/ayufan-pine64/linux-build/releases Pinebook Linux Github by ayufan]
 
* [https://github.com/ayufan-pine64/android-7.1/releases Pinebook Android Github by ayufan]
* 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.
* [https://www.armbian.com/pinebook-a64 Armbian's Pinebook Page]
 
 
----
=== 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]).
== FAQ / Tips and tricks ==


* 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.
'''Prolong battery life'''


* 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).
How to reduce the max voltage the battery is charged to?


* 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.
$ cd /sys/class/power_supply/axp20x-battery


Notice that voltage_max_design is writable by root, values are in microvolts. The factory value is 4200000 or 4.2V on my device. This charges to 100% capacity.


'''Imaging from Terminal'''
$ cat voltage_max_design
4200000


'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.
Check the factory value on your device, and record it if it is different. The value depends on the battery installed. You can reduce it to 4.1 V by running the following Linux command as root:


* 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.
$ echo 4100000 > voltage_max_design
* 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 ==
If you are fully charged and on AC, the battery will start discharging until it reaches 4.1 V. This will be about 98% capacity on my device. This prolongs the battery life when you don't need the extra few minutes of offline power. The Linux driver will not let you set the maximum voltage to a value smaller than 4.1V (as of Linux kernel 6.3.8).


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]):
The setting seems to be retained across reboots.


* Subpar or counterfeit microSD card
'''Key left of Z ( \ | )'''
* 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
How to map the key next to Z to the symbols on \ and | (rather than <>)?


* To navigate to the directory type (in terminal): ''cd /usr/local/sbin''
Choose the alternative international US keyboard layout and variant. The name will depend on your desktop environment:
* 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)


* English (US, alt. intl.)
* English (US, international AltGr Unicode combining, alternative)
* English (US, alternative international)


'''Supported Screen Resolutions'''
'''Note:''' keyboard variants with similar names as the ones above change the upper left key for ` and ~. You have to press that key twice to get the desired char. This happens with the alt-intl variant. Choose the altgr-intl variant (or however it is called in your desktop environment) and it should work as expected.


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.
To set the keyboard layout and variant in the terminal for X-Windows use:


setxkbmap -layout us -variant altgr-intl


'''Troubleshooting Step by Step'''
The Archlinux Wiki has some good help if you need to tweak your layout further [https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Setting_keyboard_layout]


Follow these steps to determine the cause of your problem:
'''Key between Fn and Alt (Menu)'''


* Check your PSU and microUSB cable ratings
How to map the key between Fn and Alt to SUPER / META ?
* 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.
The initial setup in many desktop environments maps the key between Fn and Alt to MENU. Although the menu key can be useful as well (e.g. spell correction in the browser) many desktop environments and window manager use the Super key for many other useful functions. And users are probably more used to have the META key near Ctrl and Alt.


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.
In X-windows the following command maps the key between Fn and Alt to META and the Caps-Lock key to MENU.


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
setxkbmap -option caps:menu,altwin:alt_super_win


If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/
'''Set display brightness in the terminal'''


To set the display brightness in the terminal use xbacklight (if available in your distro):


xbacklight -setXX


== Software and OS Image Downloads ==
XX is the percentage (%) of brightness. E.g. for 70% brightness


xbacklight -set70


If you use LXQt you can also use:
pkexec lxqt-backlight_backend --inc
pkexec lxqt-backlight_backend --dec


For an alternative solution please see the scripts discussed in this thread: [https://forum.pine64.org/showthread.php?tid=5062]


'''Get battery % in CLI'''


As ACPI is not compatible with ARM, to gather the % battery this can be used:


cat /sys/class/power_supply/battery/capacity


== [[Accessories_Step_by_Step_Guides|Accessories Step-by-Step Guides]] ==
'''Firefox font size'''
Under [[Accessories_Step_by_Step_Guides|'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).


How to get a useful font size with firefox ?


To have every web page displayed in a larger more readable font size type about:config in the search bar and confirm on the first page that you want to make changes. Then search for this parameter:


== SoC and Memory Specification ==
layout.css.devPixelsPerPx
* Based on Allwinner A64
[[File:Allwinner_A64.jpg]]


=== CPU Architecture ===
and modify the value (right click) to something between 1.2 to 1.5 depending on your preferences.
* [http://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php 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 ===
* [http://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php 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.


In addition to that you can set in Preferences -> General -> Fonts & Color -> Advanced Minimum font size to 16


'''Disable wireless power management'''


== Board Features ==
If having issues with wifi connectivity, try to disable power management in the 8723cs module options, adding rtw_power_mgnt=0 in /etc/modprobe.d/8723cs.conf


=== Video ===
options 8723cs rtw_initmac=00:ba:ch:16:85:46 rtw_power_mgnt=0
* HDMI 1.4a (Type A - full)


=== Audio ===
'''Touchpad acceleration and scroll direction.'''
* 3.5mm stereo earphone/microphone plug


=== Network ===
To set touchpad parameters from the cli you can use the command ''xinput''.
* 10/100/1000Mbps Ethernet(PINE A64+ version), 10/100Mbps Ethernet(PINE A64 version)
To use it correctly you first need to determine the device id / name for your touchpad. Use
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)
xinput list
to do so.
You are looking for a line like this:
HAILUCK CO.,LTD USB KEYBOARD Mouse      id=7 [slave  pointer  (2)]


=== Storage ===
With the device id = 7 found you can list the parameters that can be set with ''xinput''.
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
xinput list-props 7
* USB - 2 USB2.0 Host port


=== Expansion Ports ===
The result looks similar to this:
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
device 'HAILUCK CO.,LTD USB KEYBOARD Mouse':
* CSI - CMOS Camera Interface up to 5 mega pixel
...
* TP - Touch Panel Port, SPI with interrupt
libinput Natural Scrolling Enabled (256): 0
* RTC - Real Time Clock Battery Connector
...
* VBAT - Lithium Battery Connector with temperature sensor input
libinput Accel Speed (265): 0.000000
* Wifi/BT Module Header - SDIO 3.0 and UART
...
* 2x20 pins "Pi2" GPIO Header
* 2x17 pins "Euler" GPIO Header
* 2x5 pins "EXP" Console Header


To change the parameter use ''xinput set-prop''


To set reverse scrolling for the touchpad use this command
xinput set-prop 7 'libinput Natural Scrolling Enabled' 1


== Pine A64 Board Information and Schematics ==
To set mouse speed
* Board Dimensions: 133mm x 80mm x 19mm
xinput set-prop 7 'libinput Accel Speed' 0.95
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, microUSB connector, Euler connector
Check different numbers for 0.95 to meet your needs.
* [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/2/2e/Pine64_Board_Connector_heatsink.png PINE A64 Heat Sink Location @courtesy of norm24]
* [http://wiki.pine64.org/images/d/da/Pine64_Connector.JPG PINE A64 Connector List]
* [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]
* [http://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-Rev%20B-TOP%20Preliminary.pdf PINE A64 PCB dimension]
* [http://wiki.pine64.org/images/b/be/Pine64_Model_Spec.JPG Board Model Comparison]
* PINE A64 Board Schematic:
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20512MB%20rev%20B-2015121601_Release.pdf PINE A64 512MB Rev B Board Schematic]
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/a64-db-rev%20b-20151217-Plus-Release.pdf PINE A64+ 1GB Rev B 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]
* PINE A64 Certification:
** [http://files.pine64.org/doc/cert/Pine%20A64%20Board%20FCC%20certification%20CCF20160624.jpg PINE A64 FCC Certificate]
** [http://files.pine64.org/doc/cert/Pine%20A64%20Board%20CE%20Certification%20CCF20160624.jpg PINE A64 CE Certificate]
** [http://files.pine64.org/doc/cert/CCF20160627_00000.jpg PINE A64 RoHS Certificate]


== Datasheets for Components and Peripherals ==
For more details on xinput and mouse speed also see the Archlinux Wiki [https://wiki.archlinux.org/index.php/Mouse_acceleration#Using_xinput]
* 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_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP803 PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]
** Ethernet PHY information:
*** [http://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64+ Board]
*** [http://files.pine64.org/doc/datasheet/pine64/rtl8201cp.pdf Realtek RTL8201 10/100M Ethernet Transceiver for PINE A64 Board]
** Wifi/BT module information:
*** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** LCD Panel:
*** [http://files.pine64.org/doc/datasheet/pinebook/11.6inches-TFT-LCD%20Approval%20Specification%20N116BGE-E42%20Ver%203.0.pdf 11.6" LCD Panel datasheet]
*** [http://files.pine64.org/doc/datasheet/pinebook/14inches-HB140WX1-501(%20EDP1.2)%20Preliminary%20Product%20specification.pdf 14" LCD Panel datasheet]
** Touchpad information:
*** [http://files.pine64.org/doc/datasheet/pinebook/11-Toucpad-HK-9058%20specification.pdf Touchpad Specification for 11.6" model]
*** [http://files.pine64.org/doc/datasheet/pinebook/14-Touchpad-HK-9562%20specification.pdf Touchpad Specification for 14" model]
** Camera sensor:
*** [http://files.pine64.org/doc/datasheet/pinebook/ZC-RZ3762-3703%C2%A0S1.0-Camera-Module%20spec.pdf VGA Camera module specification]
*** [http://files.pine64.org/doc/datasheet/pinebook/VGA-CMOS-Sensor--BF3703%20Datasheet.pdf VGA Camera Sensor Data Sheet]
** Lithium Battery information:
*** [http://files.pine64.org/doc/datasheet/pinebook/PL5267103P-3.7V-10000mAh-1S2P58-9-W101-7P正向-11.6.pdf 10000mAH Lithium Battery Specification for 11.6" model]
*** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]




== Other Resources ==
[[Category:Pinebook]] [[Category:Allwinner A64]]
* [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 17:15, 27 June 2023

The Pinebook

The Pinebook is an 11.6″ or 11.6″ with 1080P IPS panel or 14″ notebook powered by the same quad-core ARM Cortex A53 64-Bit Processor used in our popular PINE A64 Single Board Computer. It is very lightweight, hackable and comes equipped with a full-sized keyboard and large multi-touch trackpad. It runs numerous mainline Linux distributions as well as *BSD and Android.

Software releases

Under Pinebook Software Releases you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

Variants

The following variants exist of the Pinebook:

  • Pinebook 11.6″
  • Pinebook 11.6″ 1080p
  • Pinebook 14″

More information can be found on the sunxi wiki.

Pinebook Service Step-by-Step Guides

These are instruction guides for the disassembly:

Note: The installation process is the reverse order of removal guide

11.6″ Pinebook:

14″ Pinebook:

Pinebook Information

  • Dimensions: 299mm x 200mm x 12mm (WxDxH - 11″ Pinebook); 329mm x 220mm x 12mm (WxDxH - 14″ Pinebook)
  • Weight: 1.04Kg (11″ Pinebook); 1.26Kg (14″ Pinebook)#
  • Input Power: DC 5V @ 3A

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:

  • System RAM Memory: 2GB
  • Storage Memory: 16GB eMMC module, can be upgrade to 32GB or 64GB eMMC module

Battery:

  • Lithium Polymer Battery (10,000mAH)

Video:

  • Mini Digital Video Port (Type A - mini)

Audio:

  • 3.5mm stereo earphone/microphone plug

Network:

  • WiFi 802.11 b/g/n with Bluetooth 4.0
  • 10/100Mbps USB Ethernet Dongle (Optional)

Storage:

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

Expansion Ports:

  • mini Digital Video port
  • microSD card port - support SD, SDHC, SDXC uo to 256GB
  • 2x USB 2.0 port
  • earphone plug with UART console mux circuit

Pinebook Schematics and Certifications

Mainboard schematics:

Daughter Board schematics:

Serial Console Earphone Jack pinout:

Certifications:

Datasheets for Components and Peripherals

Allwinner A64 SoC:

X-Powers AXP803 PMU (Power Management Unit):

LPDDR3:

eMMC:

SPI NOR flash:

WiFi/BT module:

LCD Panel:

Touchpad:

Camera sensor:

Lithium battery:

Other Resources

FAQ / Tips and tricks

Prolong battery life

How to reduce the max voltage the battery is charged to? 

$ cd /sys/class/power_supply/axp20x-battery

Notice that voltage_max_design is writable by root, values are in microvolts. The factory value is 4200000 or 4.2V on my device. This charges to 100% capacity. 

$ cat voltage_max_design 
4200000

Check the factory value on your device, and record it if it is different. The value depends on the battery installed. You can reduce it to 4.1 V by running the following Linux command as root: 

$ echo 4100000 > voltage_max_design

If you are fully charged and on AC, the battery will start discharging until it reaches 4.1 V. This will be about 98% capacity on my device. This prolongs the battery life when you don't need the extra few minutes of offline power. The Linux driver will not let you set the maximum voltage to a value smaller than 4.1V (as of Linux kernel 6.3.8).

The setting seems to be retained across reboots.

Key left of Z ( \ | )

How to map the key next to Z to the symbols on \ and | (rather than <>)?

Choose the alternative international US keyboard layout and variant. The name will depend on your desktop environment:

  • English (US, alt. intl.)
  • English (US, international AltGr Unicode combining, alternative)
  • English (US, alternative international)

Note: keyboard variants with similar names as the ones above change the upper left key for ` and ~. You have to press that key twice to get the desired char. This happens with the alt-intl variant. Choose the altgr-intl variant (or however it is called in your desktop environment) and it should work as expected.

To set the keyboard layout and variant in the terminal for X-Windows use: 

setxkbmap -layout us -variant altgr-intl

The Archlinux Wiki has some good help if you need to tweak your layout further [1]

Key between Fn and Alt (Menu)

How to map the key between Fn and Alt to SUPER / META ?

The initial setup in many desktop environments maps the key between Fn and Alt to MENU. Although the menu key can be useful as well (e.g. spell correction in the browser) many desktop environments and window manager use the Super key for many other useful functions. And users are probably more used to have the META key near Ctrl and Alt.

In X-windows the following command maps the key between Fn and Alt to META and the Caps-Lock key to MENU. 

setxkbmap -option caps:menu,altwin:alt_super_win

Set display brightness in the terminal

To set the display brightness in the terminal use xbacklight (if available in your distro): 

xbacklight -setXX

XX is the percentage (%) of brightness. E.g. for 70% brightness 

xbacklight -set70

If you use LXQt you can also use: 

pkexec lxqt-backlight_backend --inc
pkexec lxqt-backlight_backend --dec

For an alternative solution please see the scripts discussed in this thread: [2]

Get battery % in CLI

As ACPI is not compatible with ARM, to gather the % battery this can be used: 

cat /sys/class/power_supply/battery/capacity

Firefox font size

How to get a useful font size with firefox ?

To have every web page displayed in a larger more readable font size type about:config in the search bar and confirm on the first page that you want to make changes. Then search for this parameter: 

layout.css.devPixelsPerPx

and modify the value (right click) to something between 1.2 to 1.5 depending on your preferences.

In addition to that you can set in Preferences -> General -> Fonts & Color -> Advanced Minimum font size to 16

Disable wireless power management

If having issues with wifi connectivity, try to disable power management in the 8723cs module options, adding rtw_power_mgnt=0 in /etc/modprobe.d/8723cs.conf 

options 8723cs rtw_initmac=00:ba:ch:16:85:46 rtw_power_mgnt=0

Touchpad acceleration and scroll direction.

To set touchpad parameters from the cli you can use the command xinput. To use it correctly you first need to determine the device id / name for your touchpad. Use 

xinput list

to do so. You are looking for a line like this: 

HAILUCK CO.,LTD USB KEYBOARD Mouse      	id=7	[slave  pointer  (2)]

With the device id = 7 found you can list the parameters that can be set with xinput. 

xinput list-props 7

The result looks similar to this: 

device 'HAILUCK CO.,LTD USB KEYBOARD Mouse':
...
libinput Natural Scrolling Enabled (256):	0
...
libinput Accel Speed (265):	0.000000
...

To change the parameter use xinput set-prop

To set reverse scrolling for the touchpad use this command 

xinput set-prop 7 'libinput Natural Scrolling Enabled' 1

To set mouse speed 

xinput set-prop 7 'libinput Accel Speed' 0.95

Check different numbers for 0.95 to meet your needs.

For more details on xinput and mouse speed also see the Archlinux Wiki [3]

Retrieved from "https://wiki.pine64.org/index.php?title=Pinebook&oldid=19982"