https://wiki.pine64.org/api.php?action=feedcontributions&feedformat=atom&user=JerseyDevilPINE64 - User contributions [en]2026-04-23T10:36:55ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=User:JerseyDevil&diff=13238User:JerseyDevil2022-07-02T02:22:19Z<p>JerseyDevil: </p>
<hr />
<div>2022-07-01T22:03:05<br />
<br />
2021-05-12T04:39:59<br />
<br />
https://forum.pine64.org/member.php?action=profile&uid=22686<br />
<br />
----<br />
<br />
{{SeeMainArticle|User_Talk:JerseyDevil}}<br />
<br />
Feel free to create the talk page if necessary, will be archived when conversation is finished.<br />
<br />
I'll notice that the talk page no longer red-links. presumably other notices will generate, but this is one I'll be looking for.<br />
<br />
----<br />
<br />
It's funny when you hit the wiki ratelimit and it states you're adding a link when none are present in the page.<br />
<br />
also odd when the cluster starts throwing space errors on the forum and thumbnails don't generate on the wiki..<br />
<br />
capskhhhhhhskaaaaa immoral?<br />
<br />
nowiki:<br />
<nowiki><br />
[[Category:Quartz64]][[Category:Rockchip RK3566]]<br />
<br />
[[Category:PinePower]]<br />
<br />
[[Category:ROCKPro64]]<br />
<br />
[[Category:Guide]]<br />
<br />
?action=info<br />
<br />
{{SeeMainArticle|ROCK64}}<br />
<br />
[[Category:Guide]]<br />
<br />
{{toclimit|limit=1}}<br />
<br />
{{tocleft|limit=1}} <br />
<br />
{{tocright|limit=1}} <br />
<br />
__NOTOC__<br />
__FORCETOC__<br />
__TOC__<br />
<br />
floatleft<br />
floatright<br />
<br />
category:<br />
__NOGALLERY__<br />
<br />
jdjdjd@<br />
19210101<br />
<br />
<br />
</nowiki></div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PineCone&diff=13237PineCone2022-07-02T02:03:05Z<p>JerseyDevil: /* Pine64 USB JTAG Adapter information and schematics */ - correct link filename oldid=8860 - https://wiki.pine64.org/index.php?title=PineCone&diff=prev&oldid=8860 - (correct misnamed link, likely typo of ?20201218? pdf mod date.)</p>
<hr />
<div>[[File:Pine64_BL602_EVB_photo-3-small.jpg|thumb|PineCone BL602 EVB (Evaluation Board)]]<br />
<br />
The '''PineCone''' is a BL602 evaluation board, which was developed with the goal to challenge the open source community to achieve blob-free and free and open source WiFi and Bluetooth, see the [https://www.pine64.org/2020/10/28/nutcracker-challenge-blob-free-wifi-ble/ Nutcracker Challenge].<br />
<br />
== BL602 Specifications ==<br />
* '''CPU:''' 32-bit RV32IMAFC RISC-V “SiFive E24 Core”<br />
** [https://www.sifive.com/cores/e24 SiFive E24 Core information]<br />
* '''Memory:'''<br />
** 128KB ROM<br />
** 276KB SRAM<br />
** 1Kb eFuse<br />
** 2MB Embedded Flash<br />
* '''Security:'''<br />
** Secure boot<br />
** Secure debug<br />
** AES 128/192/256<br />
** SHA-1/224/256<br />
** TRNG (True Random Number Generator)<br />
** PKA (Public Key Accelerator)<br />
* '''Wireless:'''<br />
** Wi-Fi 802.11 b/g/n<br />
** Bluetooth® Low Energy 5.0<br />
** Wi-Fi Fast connection with BLE assistance<br />
** Wi-Fi and BLE coexistence<br />
** Wi-Fi Security WPS/WEP/WPA/WPA2/WPA3<br />
** STA, SoftAP and sniffer modes<br />
** Multi-Cloud connectivity<br />
** 2.4 GHz RF transceiver<br />
** Integrated RF balun, PA/LNA<br />
* '''Package Type:'''<br />
** 32 pin QFN 4mm x 4mm<br />
* JTAG support (See below for BL602 impact)<br />
<br />
[[File:BL602_Block_Diagram.jpg|600px]]<br />
<br />
== JTAG ==<br />
{| class="wikitable floatright"<br />
|+ Default JTAG pins<br />
|-<br />
| GPIO Pin || JTAG Pin<br />
|-<br />
| GPIO17 || TDI<br />
|-<br />
| GPIO11 || TDO<br />
|-<br />
| GPIO12 || TMS<br />
|-<br />
| GPIO14 || TCK<br />
|-<br />
|}<br />
<br />
BL602 multiplexes four GPIO pins to provide the familiar JTAG lines. See the accompanying table for the default pin mappings.<br />
<br />
These are the default JTAG pins in use after a cold boot. However, many pieces of software, including the demo that's installed by default on new PineCones, remap these pins to other functions. You cannot use the default wiring for JTAG while such software is running. This issue is especially prevalent on the PineCone because three of the default JTAG pins are connected to the onboard RGB LED. Nothing about the LED itself interferes with JTAG, but any program that uses the LED will necessarily remap some of the default JTAG pins to be GPIO.<br />
<br />
The MaskROM download mode that the BL602 enters when you tie GPIO8 high does '''not''' remap the default JTAG pins, and so you can and should use that mode while checking basic functionality of your JTAG adapter.<br />
<br />
Note that, just as software can remap the default JTAG pins to be something else, it can also remap other pins to be JTAG. Control over this is quite granular, with 5-6 candidate pins for each individual JTAG signal that can be mapped independently of one another. LEE Lup Yuen has written some [https://lupyuen.github.io/articles/openocd#free-the-led-from-jtag-port sample code] showing how to remap the JTAG pins so that your software can use the LED without giving up support for debugging.<br />
<br />
== Pine64 USB JTAG Adapter information and schematics ==<br />
* [https://files.pine64.org/doc/Pinenut/PINE64%20USB%20JTAG%20Adapter%20Schematic-20201215.pdf PINE64 USB JTAG Adapter Schematic-20201215.pdf (pine64_ft232hl_board-2020-12-14)] <br />
* [[:File:PINE64_USB_JTAG_Adapter_Schematic_ver_1.0a-20210109.pdf|PINE64 USB JTAG Adapter schematic 20210109 1.0a]]<br />
<br />
== PineCone BL602 EVB information and schematics ==<br />
* Approximate dimensions: 26mm x 43mm<br />
* Board layout:<br />
[[File:PADI-II_EVB.png]]<br />
* [https://files.pine64.org/doc/Pinenut/Pine64%20BL602%20EVB%20Schematic%20ver%201.1.pdf PineCone BL602 EVB schematic ver 1.1]<br />
** Note: In PineCone revision 1.1 ("BL62B_EVB V1.1" silkscreened on back of board), CC1 and CC2 share one 5.1KΩ resistor. This means the board will fail to power when you use an e-marked USB-C cable like the one that comes with Apple chargers. See [https://medium.com/@leung.benson/how-to-design-a-proper-usb-c-power-sink-hint-not-the-way-raspberry-pi-4-did-it-f470d7a5910 this article] for details of why this happens. The next schematic design will give each line its own 5.1KΩ resistor as per the USB-C specification.<br />
* The board uses a CH340 Serial/USB adapter. This chip is commonly used in Arduino-class development boards. It is a full speed (12Mbps) USB interface and has vendor ID 0x1a86 with product ID 0x7523.<br />
* The GPIO pins (11, 12, 14, 17) plus the nearby RESET, POWER, and GND pins are all located on one side of the board, on J1 to provide JTAG connection.<br />
<br />
== Pinenut-01S Module information and schematics ==<br />
[[File:Pinenut-01S_PCB-Front.png|225px]][[File:Pinenut-01S_PCB-Back.png|225px]]<br />
* [https://files.pine64.org/doc/Pinenut/Pinenut-01S%20V1.01%20SCH.pdf Pinenut-01S schematic ver 1.01]<br />
* [https://wiki.pine64.org/images/6/6b/PineNut-01S_v1.01_KiCad.zip PineNut-01S KiCad schematic ver 1.01]<br />
* [https://files.pine64.org/doc/Pinenut/NUT-01S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-01S GPIO Definition ver 1.0]<br />
* [https://files.pine64.org/doc/Pinenut/USB%20Adapter%20for%20Pinenut-01S%20Schematic%20V1.0.pdf USB Programmer adapter for Pinenut-01S schematic ver 1.0]<br />
* The default firmware runs the UART at 2000000 bps. It will accept input whilst regularly outputting:<code><br/>proc_hellow_entry: RISC-V rv32imafc<br/>cur key status:1</code><br />
<br />
== Pinenut-12S Module information ==<br />
[[File:NUT-12S_module-front.jpg|200px]][[File:NUT-12S_module-back.jpg|200px]]<br />
* [https://files.pine64.org/doc/Pinenut/NUT-12S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-12S GPIO Definition ver 1.0]<br />
* Onboard LED is connected to IO0<br />
<br />
== Datasheets for components and peripherals ==<br />
* Bouffalo BL-602 SoC information:<br />
** [https://github.com/bouffalolab/bl_docs Bouffalo Lab's official bl_docs repository]: should always contain the latest SoC documentation available, in PDF, HTML, and reStructuredText source forms.<br />
** [https://github.com/pine64/bl602-docs/tree/main/mirrored PINE64's bl602-docs repository]: contains an archive of all historical datasheets and reference manual PDFs but may lag behind Bouffalo's official repository. If you notice that it is, please submit a pull request!<br />
* USB/Serial adapter:<br />
** [https://cdn.sparkfun.com/datasheets/Dev/Arduino/Other/CH340DS1.PDF CH340 serial converter]<br />
<br />
== Misc notes ==<br />
Planned to be available in at least three form factors:<br />
* NUT-01S -> ESP-01S<br />
* NUT-12S -> ESP-12S<br />
* NUT-15 -> RTL8723/AMPAK<br />
<br />
== Loading code ==<br />
To load code, you must move the jumper to the position closest to the edge, press reset, load the code, move the jumper back toward the center of the board, and press reset again.<br />
<br />
There are currently a number of loaders in progress, each with differing degrees of completeness and success on various operating systems.<br />
* In the build tree, there is BLFlashCube for Windows, which is a proprietary GUI for flashing images. Linux and macOS binaries are available via [https://dev.bouffalolab.com/download Bouffalo Lab's developer portal].<br />
* [https://github.com/stschake/bl60x-flash bl60x-flash] is in Python and has been reported successful on MacOS catalina (10.15.6) by Punnerud and madushan1000.<br />
* [https://github.com/bouffalolab/BLOpenFlasher BLOpenFlasher] is a WIP, written in go, by Bouffalo Labs to provide source for a flash utility.<br />
* [https://github.com/renzenicolai/bl602tool bl602tool] is a Python utility in development.<br />
* <del>[https://pypi.org/project/bflb-eflash-loader/ Bouffalo's Python Flash Loader] is a new (Dec 20) flash loader by the makers of the chip.</del><br />
* <del>[https://pypi.org/project/bflb-image-build/ Bouffalo's image build] smooshes code and adds headers for downloads.</del><br />
* [https://pypi.org/project/bflb-mcu-tool/ Bouffalo's MCU tool] (Mar 2021) Python image tool replaced both of the above. Now combined with eflash loader, deals with partitions, DTS, signing, fuses etc.<br />
* [https://github.com/spacemeowx2/blflash blflash serial flasher] BL602 serial flasher, inspired by BLOpenFlasher<br />
<br />
== Development efforts ==<br />
* [https://github.com/pine64/bl_iot_sdk PineCone BL602 GitHub Page (PINE64 fork)] has compilers, linkers, and all the code to build on Windows, Linux (x86_64), and MacOS.<br />
* [https://github.com/bouffalolab/bl_iot_sdk Bouffalo Lab GitHub Page]<br />
* [https://github.com/renzenicolai/bl602-docs/ BL602 Developer organize documentation GitHub Page]<br />
* [https://github.com/renzenicolai/bl602tool BL602 Developer organize tool GitHub Page]<br />
* [https://github.com/stschake/bl60x-flash Programming tool for Bouffalo Labs BL602/BL604 chips]<br />
* [https://github.com/pine64/bl602-re BL602 reverse engineering working group]<br />
* [https://github.com/pine64/bl602-sdio-linux Linux kernel module]<br />
* [https://github.com/tchebb/bl602-docs BL602 Documentation]<br />
* [https://github.com/spacemeowx2/blflash BL602 serial flasher]<br />
* [https://github.com/mkroman/awesome-bouffalo#feature-matrix Awesome Bouffalo]<br />
<br />
== Articles and Blogs ==<br />
* [https://lupyuen.github.io/articles/pinecone Quick Peek of PineCone BL602 RISC-V Evaluation Board by Lup Yuen]<br />
* [https://maero.dk/bl602-firmware-image-format/ Documenting the BouffaloLab BL602 firmware image format by MK]<br />
* [https://lupyuen.github.io/articles/openocd Connect PineCone BL602 to OpenOCD by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/debug Debug Rust on PineCone BL602 with VSCode and GDB by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/mynewt Porting Mynewt to PineCone BL602 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/flash Flashing Firmware to PineCone BL602 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/led Control PineCone BL602 RGB LED with GPIO and PWM by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/gpio Mynewt GPIO ported to PineCone BL602 RISC-V Board by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/i2c PineCone BL602 talks to I2C Sensors by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/spi PineCone BL602 talks SPI too! by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/display PineCone BL602 Blasting Pixels to ST7789 Display with LVGL Library by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/uart PineCone BL602 Talks UART to Grove E-Ink Display by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/book The RISC-V BL602 Book by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/lora Connect PineCone BL602 to LoRa Transceiver by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/wisblock RAKwireless WisBlock talks LoRa with PineCone BL602 RISC-V Board by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/lora2 PineCone BL602 RISC-V Board Receives LoRa Packets by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/rust Run Rust RISC-V Firmware with BL602 IoT SDK by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/lorawan PineCone BL602 Talks LoRaWAN by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/lisp uLisp and Blockly on PineCone BL602 RISC-V Board by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/wasm Simulate RISC-V BL602 with WebAssembly, uLisp and Blockly by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/boot BL602 Bootloader by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/tflite Machine Learning on RISC-V BL602 with TensorFlow Lite by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/wifi Reverse Engineering WiFi on RISC-V BL602 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/adc Rust on RISC-V BL602: Is It Sunny? by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/rustsim Rust on RISC-V BL602: Simulated with WebAssembly by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/pinedio PineDio Stack BL604 RISC-V Board: Testing The Prototype by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/rhai Rust on RISC-V BL602: Rhai Scripting by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/lorawan2 LoRaWAN on PineDio Stack BL604 RISC-V Board by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/ttn The Things Network on PineDio Stack BL604 RISC-V Board by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/cbor Encode Sensor Data with CBOR on BL602 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/roblox IoT Digital Twin with Roblox and The Things Network by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/tsen Internal Temperature Sensor on BL602 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/payload CBOR Payload Formatter for The Things Network by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/prometheus Monitor IoT Devices in The Things Network with Prometheus and Grafana by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/nuttx Apache NuttX OS on RISC-V BL602 and BL604 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/spi2 SPI on Apache NuttX OS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/sx1262 LoRa SX1262 on Apache NuttX OS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/lorawan3 LoRaWAN on Apache NuttX OS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/rust2 Rust on Apache NuttX OS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/auto Auto Flash and Test NuttX on RISC-V BL602 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/loader BL602 EFlash Loader: Reverse Engineered with Ghidra by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/ikea Connect IKEA Air Quality Sensor to Apache NuttX OS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/bme280 Apache NuttX Driver for BME280 Sensor: Ported from Zephyr OS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/rusti2c Rust talks I2C on Apache NuttX RTOS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/st7789 ST7789 Display with LVGL Graphics on Apache NuttX RTOS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/pinedio2 PineDio Stack BL604 runs Apache NuttX RTOS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/touch NuttX Touch Panel Driver for PineDio Stack BL604 by Lup Yuen]<br />
* [https://www.robertlipe.com/buttons-on-bl602-nuttx/ Buttons on BL602 NuttX]<br />
* [https://lupyuen.github.io/articles/expander NuttX GPIO Expander for PineDio Stack BL604 by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/auto2 (Mostly) Automated Testing of Apache NuttX RTOS on PineDio Stack BL604 RISC-V Board by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/zig Zig on RISC-V BL602: Quick Peek with Apache NuttX RTOS by Lup Yuen]<br />
* [https://lupyuen.github.io/articles/iot Build an IoT App with Zig and LoRaWAN by Lup Yuen]<br />
<br />
[[Category:Nutcracker]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=User:JerseyDevil&diff=10809User:JerseyDevil2021-06-19T09:55:04Z<p>JerseyDevil: sorry for the wall of edits, lot's of small ones.</p>
<hr />
<div>2021-05-12T04:39:59<br />
<br />
https://forum.pine64.org/member.php?action=profile&uid=22686<br />
<br />
----<br />
<br />
{{SeeMainArticle|User_Talk:JerseyDevil}}<br />
<br />
Feel free to create the talk page if necessary, will be archived when conversation is finished.<br />
<br />
I'll notice that the talk page no longer red-links. presumably other notices will generate, but this is one I'll be looking for.<br />
<br />
----<br />
<br />
It's funny when you hit the wiki ratelimit and it states you're adding a link when none are present in the page.<br />
<br />
also odd when the cluster starts throwing space errors on the forum and thumbnails don't generate on the wiki..<br />
<br />
capskhhhhhhskaaaaa immoral?<br />
<br />
nowiki:<br />
<nowiki><br />
[[Category:Quartz64]][[Category:Rockchip RK3566]]<br />
<br />
[[Category:PinePower]]<br />
<br />
[[Category:ROCKPro64]]<br />
<br />
[[Category:Guide]]<br />
<br />
?action=info<br />
<br />
{{SeeMainArticle|ROCK64}}<br />
<br />
[[Category:Guide]]<br />
<br />
{{toclimit|limit=1}}<br />
<br />
{{tocleft|limit=1}} <br />
<br />
{{tocright|limit=1}} <br />
<br />
__NOTOC__<br />
__FORCETOC__<br />
__TOC__<br />
<br />
floatleft<br />
floatright<br />
<br />
category:<br />
__NOGALLERY__<br />
<br />
jdjdjd@<br />
19210101<br />
<br />
<br />
</nowiki></div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Accessories_Step_by_Step_Guides&diff=10808Accessories Step by Step Guides2021-06-19T09:03:26Z<p>JerseyDevil: category</p>
<hr />
<div>Accessories Step by Step Guides<br />
==Wifi/Bluetooth module:==<br />
*[http://files.pine64.org/doc/guide/PINE64_Wi-Fi_Bluetooth_Installation_Guide.pdf Step by Step Installation Guide]<br />
==Acrylic Open Enclosure:==<br />
*[http://files.pine64.org/doc/guide/PINE64_Acrylic_Open_Enclosure_Installation_Guide.pdf Step by Step Installation Guide]<br />
<br />
If you wish to stack two or more of these enclosures, the screws that serve as feet can be replaced by M8-1.25x16mm grub screws.<br />
<br />
<blockquote><br />
1.25mm is the pitch between threads, and for the M8 (8mm outer diameter) that's the default pitch, and most are advertised as M8x16mm screws. 16mm is really the minimum workable length to catch both the bottom and top aluminium standoffs, with both washers and the acrylic sheet in between. It's workable, but if you can get 20mm it's probably for the best.<br />
</blockquote><br />
<br />
Images: https://imgur.com/a/Zka1qfb<br />
<br />
==Simple 3D Printed Case by Harlandraka==<br />
*[http://www.thingiverse.com/thing:1831345 3D printing schematics]<br />
==Sliding 3D Printed Case by Harlandraka==<br />
*[http://www.thingiverse.com/thing:1694943 3D printing schematics]<br />
==C4 Labs Case for the Pine==<br />
*[http://forum.pine64.org/showthread.php?tid=2277 Forum thread including instructions]<br />
==7" LCD Touch Screen Panel:==<br />
*[http://files.pine64.org/doc/guide/PINE64_7_inches_LCD_Touch_Screen_Panel_Installation_Guide.pdf Step by Step Installation Guide]<br />
==Real Time Clock (RTC) battery holder (AAA battery type):==<br />
*[http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_AAA_Installation_Guide.pdf Step by Step Installation Guide]<br />
==Real Time Clock (RTC) battery holder (CR-2032 Coin Cell battery type):==<br />
*[http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_CR2032_Installation_Guide.pdf Step by Step Installation Guide]<br />
<br />
[[Category:Pine A64]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PineTime_Custom_Watchface_Tutorial&diff=10807PineTime Custom Watchface Tutorial2021-06-19T09:00:47Z<p>JerseyDevil: category</p>
<hr />
<div>=PineTime Custom Watchface Tutorial=<br />
<br />
This is a tutorial to help new users create custom watchfaces based on the InfiniTime Firmware for Pinetime made by user JF002, thanks to him for its development...<br />
<br />
We will explain some of the things we went through while creating some custom Watchfaces, so consider this as a log of experiments of sorts..<br />
<br />
So stay tuned to it as it will be dynamically updated...<br />
<br />
==What you need to start==<br />
The entire building process will be done by GitHub, so all you need is a device which can give you a Github Web Client, a PC or tablet to give you enough screen space to review your code and a steady internet connection.<br />
<br />
Since the compiling and file management is done by Github online, you have nothing else to worry about other than working with the files that display the watch face.<br />
<br />
So with those things settled, let's start with the basics of a watchface.<br />
<br />
Please remember that this is a wiki, so you can make an account and help us improve this page.<br />
<br />
Please make sure not to unilaterally remove info though, but offer an alternative. If it is indeed a better way, in time your alternative will grow into the main text, and the latter info will be pruned.<br />
<br />
==Overview==<br />
The Firmware (also called InfiniTime) we will be working with is made with a programming language named '''C++''':[https://en.wikipedia.org/wiki/C%2B%2B]<br />
<br />
Basic knowledge of C/C++ is required to to understand the advanced watch faces as that requires more complex code, but you can still do a some cool things without much knowledge of C++ programming, just some small edits to existing programs.<br />
<br />
InfiniTime uses the '''LVGL''':[https://lvgl.io] graphics library to provide users with a simple and clean UI without overpowering the Nordic '''nRF52832''':[http://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf] microcontroller which is the brain of the watch.<br />
<br />
To get the watchface to work there are these basic steps. We will go over each step separately, so don't be daunted, all will become clear soon.<br />
<br />
For now we will, modify the the existing watchface, change the positioning of the text labels, add an icon to an existing watchface, and later on we will do a full watchface.<br />
<br />
<br />
<br />
The main file we need to focus on is the '''WatchFaceDigital.cpp''' file, it is what contains most of the data attributed to what we see on the watchface, including The time/day characters, the battery and bluetooth icons, and also pedometer count...<br />
<br />
so everything we will be doing in the basic modifications is purely messing with this single file.<br />
<br />
==Labels==<br />
===What are labels?===<br />
Labels are considered as "elemental" parts that make up a screen's Text-based UI by the LVGL library...<br />
Each label is also considered as an "object" or "obj" and can be manipulated, by changing the data attributed with the "obj", for example, position, internal data like the strings/text etc.<br />
when can change what the label shows and where it shows it...<br />
<br />
===Modifying label data===<br />
let's observe something small like the word "BPM" near the bottom of the watch face...<br />
[[file:PineTimeCustom-1.png|right|200px]]<br />
<br />
If we take a look at the source file of the watchface, (a.k.a the clock.cpp file)<br />
we can observe that these particular lines are what attributes to the word "BPM being displayed...<br />
heartbeatBpm = lv_label_create(lv_scr_act(), NULL);<br />
lv_label_set_text(heartbeatBpm, "BPM");<br />
<br />
we can modify the text inside the quotes and replace the word 'BPM' between those quotes to something like 'LOVE'<br />
and the result after compiling the firmware again with the changes and flashing it to the watch would be that the text changes on the watch face and displays 'LOVE' inplace of 'BPM'...<br />
<br />
If this happened correctly, then you have successfully made a custom new watchface! Now we can do something a bit more complex...<br />
<br />
<br />
<br />
Now take for in instance the days of the week that we have on the bottom line with the date...<br />
<br />
they are stored a "C array" which is basically multiple words separated by commas..<br />
the date is in a format of '''<day of the week> <day> <Month> <year>'''<br />
<br />
which in the source file is expressed as,<br />
sprintf(dateStr, "%s %d %s %d", DayOfWeekToString(dayOfWeek), day, MonthToString(month), year);<br />
lv_label_set_text(label_date, dateStr);<br />
<br />
here, <br />
%s %d %s %d <br />
stores the print format of the variables, and<br />
<br />
DayOfWeekToString(dayOfWeek), day, MonthToString(month), year <br />
are the variables themselves...<br />
<br />
Now, <br />
if the date was a saturday 11/7/2020, you can observe that the date looks like <br />
SATURDAY 11 JUL 2020<br />
as seen in the above image (the one where we changed BPM to LOVE)<br />
<br />
by modifying the format of the variables, we can change how those words are arranged, and add some extra characters if we like... <br />
(there is a catch to the list of characters you can use however, but it will be discussed later...)<br />
<br />
For example,<br />
<br />
We modifying the format by adding a comma... "," in between the second "%s" and "%d" like this,<br />
"%s %d %s, %d"<br />
and changing that in the line...<br />
sprintf(dateStr, "%s %d %s, %d", DayOfWeekToString(dayOfWeek), day, MonthToString(month), year);<br />
<br />
we can make the date become...<br />
SATURDAY 11 JUL, 2020<br />
<br />
which means we now were able to modify how the text got display to make it a bit more nice...<br />
<br />
but if you haven't noticed, the line containing the date is already full, meaning we will get some problems while displaying the date and causing it to wrap around,<br />
making a single character go to the next line and look more like,<br />
<br />
SATURDAY 11 JUL, 202<br />
0<br />
<br />
so why don't we shorten the characters present in the date from being "SATURDAY" to simply just "sat." (It will have the small period at the end, and is only 3 characters long) <br />
I will also convert the months of the year from Capital to small letters... <br />
<br />
for that look into the part where the days of the week of are stored as text,<br />
and also while looking at it, we can solve another question, why was their two variables in the date format that looked like, DayOfWeekToString(dayOfWeek), and MonthToString(month) ?<br />
<br />
It is because the system gives the date/ time as numbers (Monday-1, Tuesday-2 Wednesday-3 for the days, and 1-January, 2-February, 3-March ),<br />
and so a function along with a C array is used to assign these numbers to Days/Months in text form as it is easier to read...<br />
<br />
<br />
<br />
this is the Array containing the day of the week, (as text) <br />
char const *Clock::DaysString[] = {<br />
"",<br />
"MONDAY",<br />
"TUESDAY",<br />
"WEDNESDAY",<br />
"THURSDAY",<br />
"FRIDAY",<br />
"SATURDAY",<br />
"SUNDAY"<br />
};<br />
<br />
and this Array stores the months of the year, (as text)<br />
char const *Clock::MonthsString[] = {<br />
"",<br />
"JAN",<br />
"FEB",<br />
"MAR",<br />
"APR",<br />
"MAY",<br />
"JUN",<br />
"JUL",<br />
"AUG",<br />
"SEP",<br />
"OCT",<br />
"NOV",<br />
"DEC"<br />
};<br />
<br />
here we can see that the days are stored in a full format as "SUNDAY", "MONDAY", "TUESDAY" etc.<br />
we can change all of them to a shorter format like "sun.", "mon.", "tue.", to make it short and nice...<br />
while doing so, we can even make the months use small letters as said before..<br />
<br />
so the source file (clock.cpp) becomes,<br />
<br />
(for the days of the week)<br />
char const *Clock::DaysString[] = {<br />
"",<br />
"mon.",<br />
"tue.",<br />
"wed.",<br />
"thu.",<br />
"fri.",<br />
"sat.",<br />
"sun."<br />
};<br />
<br />
and<br />
<br />
(for the months of the year)<br />
char const *Clock::MonthsString[] = {<br />
"",<br />
"jan",<br />
"feb",<br />
"mar",<br />
"apr",<br />
"may",<br />
"jun",<br />
"jul",<br />
"aug",<br />
"sep",<br />
"oct",<br />
"nov",<br />
"dec"<br />
};<br />
<br />
which means now our original date, saturday 11/7/2020 will become...<br />
sat. 11 jul, 2020<br />
<br />
you now know how to change the data present in a label object, and the format of it..,<br />
<br />
Here is a fun idea you can try: you can even replace the days with whatever thing that tells you (or) reminds you the day of the week <br />
(like the food served in the cafe, Monday/taco, Tuesday/burger, Wednesday/pasta etc.) <br />
<br />
NOTE: when making the custom array, don't forget to leave a empty "" as the first element of the array,<br />
This is because the date is given by the system in a natural numbers format (1,2,3...) rather than a zero-starting format (0,1,2,3...), which the C array uses to index...<br />
so the C array indexes the days as ""-0, "Monday"-1, "Tuesday"-2 etc. and the months as ""-0, "January"-1, "February"-2 etc.)<br />
<br />
===Label positioning===<br />
<br />
The locational placement in LVGL is done on a cartesian plane,<br />
where each object can have dynamic origin placement, and the Y-axis is inverted...<br />
So going down is done with a positive Y-axis value and not negative as the it is by de-facto...<br />
<br />
[[File:LVGL coord system.png|200px|thumb|right|LVGL coord system]]<br />
<br />
The position of the various objects in clock.cpp are set by the line,<br />
lv_obj_set_pos(<obj>, <new_x>, <new_y>)<br />
<br />
and the top left corner is the Cartesian origin, aka coordinates (0,0)<br />
<br />
this image can show you how to decide label placement for lv_obj_set_pos(...)<br />
<br />
<br />
<br />
<br />
<br />
we use another function, that is more advanced that gives the positional alignment based on preset locations...<br />
lv_obj_align(<text/obj>, <image/obj>, <location_parameter>, <new_x>, <new_y>);<br />
<br />
the "<image/obj>" data is used for putting text beside other picture icons , and so if using only text based labels, we can substitute it with,<br />
lv_scr_act() (or) NULL<br />
<br />
'''<new_x>, <new_y>''' are the cartesian coordinates, '''<location parameter>''' is replaced by '''LV_ALIGN_<preset>''',<br />
there will be a picture showing the presets below, and '''<text/obj>''' is your text label...<br />
<br />
here, LV_ALIGN_<preset> sets the cartesian origin...<br />
<br />
Label positioning based on alignment is both a simple and complicated thing to understand, so here I have given something you can refer to while modifying the position of the various labels and objects...<br />
<br />
you can also refer here for LVGL's documentation of coordinate system https://docs.lvgl.io/v6/en/html/object-types/obj.html#coordinates<br />
<br />
It is however recommended that you use the first method to set the location<br />
lv_obj_set_pos(<obj>, <new_x>, <new_y>)<br />
as it is simple and easier for beginners<br />
<br />
<br />
<br />
Here is a small example.<br />
<br />
Take the Label that tells the date,<br />
In the source file (clock.cpp) it is this line,<br />
lv_obj_align(label_date, lv_scr_act(), LV_ALIGN_IN_LEFT_MID, 0, 60);<br />
by increasing the Value of the Y coordinate (60) to a higher value, we can bring the position of the Date downwards a bit away from the Time, and toward the Heartbeat count in the bottom row<br />
here I will increase it to 80, so it becomes..<br />
lv_obj_align(label_date, lv_scr_act(), LV_ALIGN_IN_LEFT_MID, 0, 80);<br />
<br />
and now we have made some space up top..<br />
<br />
<br />
now let's try something a bit complex,<br />
<br />
Take the position argument for the label that tells you time...<br />
here, in the source file (clock.cpp),<br />
lv_obj_align(label_time, lv_scr_act(), LV_ALIGN_IN_LEFT_MID, 0, 0);<br />
<br />
this line determines the position of the Label telling time, as seen in the image...<br />
<br />
we modifying this, by changing the origin <preset> parameter (here it is LV_ALIGN_IN_LEFT_MID) to LV_ALIGN_IN_TOP_LEFT<br />
<br />
you can alternatively swap the whole line to,<br />
lv_obj_set_pos(label_time, 0, 0);<br />
<br />
this makes the Time label/obj. to go to the top left corner...<br />
<br />
but I will do something a little extra,<br />
I will modify the label that store the data and Time format,<br />
i.e this line,<br />
sprintf(timeStr, "%c%c:%c%c", hoursChar[0],hoursChar[1],minutesChar[0], minutesChar[1]);<br />
<br />
by removing the ":" colon in between the numbers, and replacing it with a Newline symbol "\n"<br />
I change it to become,<br />
sprintf(timeStr, "%c%c\n%c%c", hoursChar[0],hoursChar[1],minutesChar[0], minutesChar[1]);<br />
<br />
this gives it a nice wrapped text format in the top corner, and gives us some space to play with in the side, for things like Pictures and icons, which we will do next..<br />
<br />
If you have been able to do these things, you now have completed the 2nd part of the tutorial, and now know how to change and modify the position of labels..<br />
<br />
==Using icons==<br />
The LVGL library allows for the use of widgets known as "Images", In short it allows you to use small Icons like pictures with a small dedicated function,<br />
However when this was attempted the first time we stumbled on some problems as LVGL v6 (used on the pinetime) is not much documented as the latest release (v7 as of August 2020) <br />
but also the existing code was only documented for C not C++, after some painful attempts we were able to translate it into C++, <br />
<br />
To bring images into Clock.cpp<br />
you will need to do the following,<br />
<br />
1. Have a small image that cannot exceed a maximum size of 240px x 240px (pinetime max resolution)<br />
<br />
2. Use this Image converter (Thanks to LVGL) https://lvgl.io/tools/imageconverter<br />
to convert your image to a C array and having the Color format as "True color" and the output format as "C array"<br />
make sure to use something simple as the name we will be using "bitmap" as the name, but will also be referred as <name> for simplicity<br />
<br />
Note: for example we shall use <name> = bitmap, but any simple word can be used, as long as it does not cause problems with system variables<br />
<br />
===Image size considerations===<br />
since the image will be using the flash directly, we need to be considerate about flash memory usage.<br />
<br />
<picture_X> x <picture_Y> x 2 <br />
gives you the number of KB the image used in storage...<br />
<br />
where, <picture_X> <picture_Y> are the dimensions of the image horizontally and vertically<br />
<br />
for example,<br />
if <picture_X>=80px <picture_Y>=64px<br />
then,<br />
total storage used = 80 x 60 x 2 = 10.24KB <br />
<br />
please use the flash storage with consideration, when using other apps as well, excess usage of storage <br />
might mean the Firmware will not compile... the limit to storage to about 400Kb for the user, the <br />
firmware size must not exceed that...<br />
<br />
==Preparing the image for inclusion as an icon==<br />
<br />
Once you have your obtained your C array from the LVGL converter, you can take a look inside it to see all the different formats of your image, <br />
try using something like Notepad++ or any of your favorite text editors to peek inside of it,<br />
<br />
there will be 4 sets of Arrays inside it that look like,<br />
<br />
#if LV_COLOR_DEPTH == 1 || LV_COLOR_DEPTH == 8<br />
/*Pixel format: Red: 3 bit, Green: 3 bit, Blue: 2 bit*/<br />
0x00, 0x00, 0x00,...<br />
...0x00, 0x00, 0x00, <br />
#endif<br />
<br />
#if LV_COLOR_DEPTH == 16 && LV_COLOR_16_SWAP == 0<br />
/*Pixel format: Red: 5 bit, Green: 6 bit, Blue: 5 bit*/<br />
0x00, 0x00, 0x00,...<br />
...0x00, 0x00, 0x00, <br />
#endif<br />
<br />
#if LV_COLOR_DEPTH == 16 && LV_COLOR_16_SWAP != 0<br />
/*Pixel format: Red: 5 bit, Green: 6 bit, Blue: 5 bit BUT the 2 bytes are swapped*/<br />
0x00, 0x00, 0x00,...<br />
...0x00, 0x00, 0x00, <br />
#endif<br />
<br />
#if LV_COLOR_DEPTH == 32<br />
/*Pixel format: Fix 0xFF: 8 bit, Red: 8 bit, Green: 8 bit, Blue: 8 bit*/<br />
0x00, 0x00, 0x00,...<br />
...0x00, 0x00, 0xff, <br />
#endif<br />
};<br />
<br />
And another small bit of info we will need for later that looks like,<br />
<br />
const lv_img_dsc_t bitmap = {<br />
.header.always_zero = 0,<br />
.header.w = 40,<br />
.header.h = 40,<br />
.data_size = 1600 * LV_COLOR_SIZE / 8,<br />
.header.cf = LV_IMG_CF_TRUE_COLOR,<br />
.data = bitmap_map,<br />
};<br />
<br />
NOTE: There are some header files at the top, which we can ignore...<br />
===RGB565 image format===<br />
<br />
The Pinetime uses a display that uses a 16 bit color space, also known as RGB565.<br />
<br />
These 16 bit are assigned to RGB as 5 bits each for Red and Blue and 6 bits for Green, so 5+6+5=16 bits are required, so each pixel's color occupies 2 bytes of data,<br />
and since 2<sup>16</sup> is equal to 65,536 it allows us to view 65,536 or 65k colors<br />
<br />
The way it packs these bits is by converting the bits into 2x 4+4 bit hex-code, so for example,<br />
<br />
if the color of a pixel in Binary is '''10110100 01011111''' (this color is approximately Lavender purple)<br />
<br />
It is split as '''1011''' & '''0100''' for the first byte and '''0101''' & '''1111''' for the second byte<br />
and so, converting the binary into Hex-code,<br />
<br />
the two parts are '''0xB4''' and '''0xF5'''<br />
<br />
These two parts in conjunction are used for determining the color of one pixel...<br />
<br />
also from the binary, it is observed that,<br />
<br />
The bits '''10110''' is used for Red, '''100010''' is used for green, and '''11111''' is used for blue.<br />
<br />
===Flipping the bytes===<br />
The LVGL library has a feature that allows you to flip the two bytes of the pixel, so if the two parts were, ...0xB4,0xF5,... ,it will change it to become, ...0xF5,0xB4,...<br />
<br />
The reason for this is to allow the use of 8-bit SPI interfaces, but we do not require it, and if set with wrong parameter we could get problems with the color...<br />
<br />
To make sure you are ready for the next step, make sure that inside your lvgl configuration file (located at '''src/libs/lv_conf.h''')<br />
<br />
this parameter, <br />
'''#define LV_COLOR_16_SWAP 1'''<br />
is set to "1" as seen...<br />
<br />
NOTE: if you haven't modified it or tampered with it with your Github fork, you shouldn't have a problem <br />
as it is correct by default, and you can skip these steps<br />
<br />
===Creating an Object from the Array===<br />
To include the Icon, first Identify the Array you need to copy to the source (clock.cpp)<br />
<br />
The one we require from it is the data below the tag that looks like,<br />
#if LV_COLOR_DEPTH == 16 && LV_COLOR_16_SWAP != 0<br />
/*Pixel format: Red: 5 bit, Green: 6 bit, Blue: 5 bit BUT the 2 bytes are swapped*/<br />
0x00, 0x00, 0x00,...<br />
...0x00, 0x00, 0x00, <br />
#endif<br />
<br />
from this copy the Data from the array alone...<br />
I.e this part,<br />
0x00, 0x00, 0x00,...<br />
...0x00, 0x00, 0x00<br />
<br />
(Make sure to not include the comma at the end or the #endif as the entire part is going to substitute a new array)<br />
<br />
In clock.cpp, just below the header files and the Task creation part (I.e event_handler...),<br />
<br />
static void event_handler(lv_obj_t * obj, lv_event_t event) {<br />
Clock* screen = static_cast<Clock *>(obj->user_data);<br />
screen->OnObjectEvent(obj, event);<br />
}<br />
<br />
create a name for the label with,<br />
static lv_img_dsc_t <name>; // remember to replace <name> with the actual name you gave to your image while converting !<br />
<br />
then below it create a array to hold the data with,<br />
const uint8_t <name>_map[] = {}; // paste the array you copied from the conversion file we specified above...<br />
<br />
so your array is something like,<br />
<br />
const uint8_t <name>_map[] = {0x00,0x00,0x00...<br />
...0x00,0x00,0x00};<br />
<br />
so your Entire top region of declaration looks like,<br />
<br />
#include <cstdio><br />
#include <libs/date/includes/date/date.h><br />
...<br />
using namespace Pinetime::Applications::Screens;<br />
extern lv_font_t jetbrains_mono_extrabold_compressed;<br />
extern lv_font_t jetbrains_mono_bold_20;<br />
extern lv_style_t* LabelBigStyle;<br />
''' '''<br />
static void event_handler(lv_obj_t * obj, lv_event_t event) {<br />
Clock* screen = static_cast<Clock *>(obj->user_data);<br />
screen->OnObjectEvent(obj, event);<br />
}<br />
''' '''<br />
'''//Declare the descriptor here'''<br />
static lv_img_dsc_t <name>;<br />
'''//place the Image data here<br />
const uint8_t <name>_map[] = {0x00,0x00,0x00...<br />
...0x00,0x00,0x00<br />
};<br />
<br />
<br />
'''note: Declaring variables outside a function like we did above is known as global scope declaration, this means the variable can be used by not just one function but the Entire code...'''<br />
<br />
<br />
Then inside the <br />
Clock::Clock(DisplayApp* app,...){... <br />
region, (the watchface function)<br />
You need to place a particular set of lines which LVGL uses to define the object declare the array as an Icon/Image, You can place this set of lines above label_time...<br />
<br />
<name>.header.always_zero = 0; //Initialization<br />
<name>.header.w = <picture_X>; // Setting the Width (or) Horizontal length of the image (number of px)<br />
<name>.header.h = <picture_Y>; // Setting the Height (or) vertical length of the image (number of px)<br />
<name>.data_size = <Hr_length> * <Vr_length> * LV_COLOR_SIZE / 8; //Allocation of memory for the image<br />
<name>.header.cf = LV_IMG_CF_TRUE_COLOR; // Sets the color scheme for the image<br />
<name>.data = <name>_map; // Maps the Image data to the Array<br />
lv_obj_t *img_src = lv_img_create(lv_scr_act(), NULL); // Create an image object<br />
lv_img_set_src(img_src, &<name>); // Set the created file as image (<name>)<br />
<br />
again, make sure to replace <name> with the name you gave it during conversion!<br />
<br />
Now that we have bought in the image data, we need to set the position, you can place this just below the lines we wrote for bringing in the image, It can be done with either,<br />
lv_obj_set_pos(img_src, <x_pos, <y_pos>); // <x_pos>, <y_pos> are the coordinates of the cartesian plane<br />
or,<br />
lv_obj_align(img_src, lv_scr_act(), LV_ALIGN_<parameter>, <x_pos, <y_pos>); <br />
<br />
If done correctly, you will now have a beautiful little Icon/Image in your Watch face,<br />
Make sure that your Watch face can accommodate the Image by pushing the other labels farther away creating space for it...<br />
<br />
We have provided a small template you can use for adding even a large image comfortably<br />
<br />
If you have succeeded with this, you have completed part 3 of the tutorial.<br />
<br />
=Creating an entirely new watchface=<br />
The instructions above describe how to modify the existing default watchface, if you would like to create a new watchface instead you will need to complete some additional steps. We will refer to the new watchface as WatchFaceName in these instructions.<br />
<br />
==Create the watchface files==<br />
The watchface is composed of 2 files, WatchFaceName.cpp and WatchFaceName.h. You can copy them from one of the existing watchfaces and give it a new name to provide a basic layout to start from. It is important to increment the ClockFace number near the top of WatchFaceName.cpp otherwise the wrong watchface will be displayed when leaving the menu.<br />
settingsController.SetClockFace(0);<br />
<br />
==Add the watchface to Clock.cpp and Clock.h==<br />
Clock.cpp now provides the ability to switch between multiple watchfaces by long-pressing the screen. You will need to make 3 modifications in Clock.cpp and 2 modifications in Clock.h. <br />
<br />
'''src/displayapp/screens/Clock.cpp'''<br />
#include "WatchFaceDigital.h"<br />
#include "WatchFaceAnalog.h"<br />
'''#include "WatchFaceName.h"'''<br />
<br />
[this]() -> std::unique_ptr<Screen> { return WatchFaceDigitalScreen(); },<br />
[this]() -> std::unique_ptr<Screen> { return WatchFaceAnalogScreen(); },<br />
'''[this]() -> std::unique_ptr<Screen> { return WatchFaceNameScreen(); },'''<br />
<br />
std::unique_ptr<Screen> Clock::WatchFaceAnalogScreen() { <br />
return std::make_unique<Screens::WatchFaceAnalog>(app, dateTimeController, batteryController, bleController, notificatioManager, settingsController);<br />
}<br />
<br />
'''std::unique_ptr<Screen> Clock::WatchFaceNameScreen() { '''<br />
'''return std::make_unique<Screens::WatchFaceName>(app, dateTimeController, batteryController, bleController, notificatioManager, settingsController, heartRateController);'''<br />
'''}'''<br />
<br />
'''src/displayapp/screens/Clock.h'''<br />
ScreenList<'''3'''> screens;<br />
std::unique_ptr<Screen> WatchFaceDigitalScreen();<br />
std::unique_ptr<Screen> WatchFaceAnalogScreen();<br />
'''std::unique_ptr<Screen> WatchFaceNameScreen();'''<br />
<br />
Be sure to increment the number of screens.<br />
<br />
==Add the watchface to CMakeLists.txt==<br />
'''src/CMakeLists.txt'''<br />
<br />
## Watch faces<br />
displayapp/icons/bg_clock.c<br />
displayapp/screens/WatchFaceAnalog.cpp<br />
displayapp/screens/WatchFaceDigital.cpp<br />
'''displayapp/screens/WatchFaceName.cpp'''<br />
<br />
=Using git to work on the firmware=<br />
===Cloning the repository===<br />
<br />
Instructions for cloning the repository are available on the [https://github.com/JF002/InfiniTime/blob/develop/doc/buildAndProgram.md Building and programming page] on github.<br />
<br />
===Changing the code to add the image===<br />
<br />
Use the editor of your choice to modify the source files. Please read the [https://github.com/JF002/InfiniTime/blob/develop/doc/contribute.md#coding-convention coding conventions] before you start.<br />
<br />
===Compiling the firmware===<br />
<br />
Information about how to compile the firmware is included on the [https://github.com/JF002/InfiniTime/blob/develop/doc/buildAndProgram.md Building and programming page] on github.<br />
<br />
==Testing the firmware==<br />
===Installing the new firmware===<br />
<br />
A holistic guide on how to install different firmware using various hardware programmers is available here: [[Reprogramming the PineTime]].<br />
<br />
If you would like to install the firmware by OTA/DFU, you can follow these steps:<br />
cmake -DARM_NONE_EABI_TOOLCHAIN_PATH=/path/to/gcc-arm-none-eabi-9-2020-q2-update -DNRF5_SDK_PATH=/path/to/nRF5_SDK_15.3.0_59ac345 -DUSE_OPENOCD=1 -DBUILD_DFU=1 ../<br />
make -j pinetime-mcuboot-app<br />
<br />
Be aware the paths for the cmake command must be absolute. The -DBUILD_DFU argument will generate a zip file which can be flashed using nRF Connect or Gadgetbridge on Android. You must have adafruit-nrfutil installed in your $PATH for this to work.<br />
<br />
===Activating the firmware===<br />
<br />
<br />
===How to troubleshoot===<br />
==Conclusions==<br />
==Next steps==<br />
==More in-depth documentation==<br />
==Thanks for the help==<br />
<br />
[[Category:PineTime]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Pinebook_Pro_Troubleshooting_Guide&diff=10784Pinebook Pro Troubleshooting Guide2021-06-19T07:38:36Z<p>JerseyDevil: category</p>
<hr />
<div><br />
=Useful Links=<br />
<br />
[[Pinebook_Pro|Back to the main Pinebook Pro page]]<br />
<br />
[[Pinebook_Pro_Hardware_Accessory_Compatibility|Hardware Compatibility page]]<br />
<br />
[[Pinebook Pro Software Release]]<br />
<br />
<br />
=Tips, tricks and other information for troubleshooting your Pinebook Pro=<br />
<br />
If something has gone wrong, the key thing is remain calm and not do anything hasty and make things worse, particularly when flashing the eMMC or firmware. Try and make a record of all the things you did in the run-up to the problem (even to the point of using a camera to take a note of errors on the screen, this record can be vital later).<br />
<br />
=Manjaro Updates Fail With 404=<br />
If you have an old Manjaro installation then it will have the wrong repositories/mirrors set up and they won't work. Set up new repositories by following these instructions:<br />
https://forum.manjaro.org/t/another-mirror-transition-manual-intervention-required/132302<br />
<br />
=Power And Boot=<br />
<br />
== New from the factory - Pinebook Pro won't boot / power on ==<br />
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC.<br />
* The eMMC may have come loose during shipment. [[Pinebook Pro#Accessing the Internals - Disassembly and Reassembly|Open the back]] and verify that the eMMC is firmly seated.<br />
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.<br />
* It's possible that your eMMC is empty from the factory. Simply [[NOOB|create]] a bootable [[Pinebook_Pro#Pinebook_Pro_images|SD card]] and see if your Pinebook Pro [[Pinebook_Pro#Boot_sequence_details|boots]]. If so, you can then [[NOOB|write]] an OS image to the eMMC.<br />
<br />
== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ==<br />
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).<br />
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.<br />
<br />
== Pinebook Pro will not power on after removing and replacing EMI shielding ==<br />
* Closely inspect that the shielding is firmly seated in the clips on all sides. You can be seated in the clips on one axis, and have missed on an another axis.<br />
<br />
== Pinebook Pro won't boot when using UART console cable ==<br />
* If you're using the [[Pinebook_Pro#Using_the_UART|UART]] cable sold on the [https://pine64.com/product-category/pinebook-pro/ Pine Store], you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.<br />
* Make sure your USB to serial UART device is 3.3v. Many are 5v and some even +-12v. Pinebook Pro's only support 3.3v and may act eratically when using higher voltage. Further, higher voltage could permananetly damage the Pinebook Pro's SoC.<br />
<br />
== Pinebook Pro will not sleep with lid closed ==<br />
A problem with the positioning of the lid magnet has been identified by several forum users in mid-2020 models of the Pinebook Pro. The magnetic field from the lid magnet operates a hall effect sensor located on the daughterboard (smallboard), which causes the Pinebook Pro to sleep when the lid is closed. If the magnet is not positioned correctly, the Pinebook Pro will not sleep when the lid is fully closed, but may sleep if the lid is open about an inch. If you experience this problem, repositioning of the magnet may be necessary.<br />
=== Lid Magnet Repositioning Step-by-Step ===<br />
*Read these steps thoroughly before starting. This is a somewhat laborious process involving fragile parts!<br />
# Remove bottom cover.<br />
# Disconnect LCD and webcam ribbon cable from main board. Flip the small black strip on the connector upward and the ribbon cable can be easily removed. Do not pull the cable out without first raising the black retaining mechanism.<br />
# Remove the small black plastic standoffs on each hinge and set aside.<br />
# Remove the three screws from each hinge on the display assembly.<br />
# Move the hinges upward to a 90 degree angle independently from the main body. Then lift the main body to the same 90 degree angle and you should be able to separate the display assembly from the main body. Set the main body aside.<br />
# Remove the plastic hinge cover on the display assembly. There's not really an easy way to do this, just work slowly and deliberately so as not to damage the sensitive cable inside. Start from either end and work your way inward. Use a small flathead screwdriver or similar tool to get started.<br />
# Remove the hinges from the display assembly.<br />
# Remove the rubber bumpers at the top corners of the display assembly to expose two screws. Remove the screws.<br />
# Starting at the corners, separate the bezel from the lid. The clips that hold it in place are similar to those found on the hinge cover. Again, slow deliberate work will get it done. Work from the top down. Take care not to damage the cables in the bottom.<br />
# With the bezel separated from the lid, feed the cable through the slot and set the bezel aside.<br />
# Without removing the LCD panel completely, lift and move the panel slightly to the left, taking care not to damage the cable running underneath up to the webcam. This will give you room to remove the magnet without risking damage to the panel.<br />
# The magnet is a silver colored bar near the bottom right side of the lid. Pry the magnet out with a small flathead or similar tool and set it aside. There is some adhesive but it's not very strong.<br />
# Put the LCD panel back where it belongs. Note the foam pads on either side of the panel. The magnet is the same width as the foam pad that keeps the panel in place, and should fit perfectly in the same channel.<br />
# The magnet should be placed about 1 to 1.5cm lower than where it was originally. There should be no need for adhesive, as the magnet will stick to the LCD panel. For reference, the hall effect sensor that the magnet interacts with is in between the USB port and audio jack.<br />
# Reassemble using these steps in reverse order.<br />
<br />
Your PineBook Pro should now sleep properly when the lid is closed.<br />
<br />
=WiFi And Bluetooth=<br />
<br />
== WiFi issues ==<br />
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro#Privacy_Switches|Privacy Switches]]<br />
* Next, you may have to modify the <code>/etc/NetworkManager/NetworkManager.conf</code> as root user, and replace <code>managed=false</code> with <code>managed=true</code>. Then reboot.<br />
* For connections that drop and resume too often, it might be due to WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. (Power management can be turned off via command line with <code>iw dev wlan0 set power_save off</code> or <code>iwconfig wlan0 power off</code>, although it is not persistent through re-boot.)<br />
* For connections that drop under load on the default Debian, remove <code>iwconfig wlan0 power off</code> in the file <code>/etc/rc.local</code>.<br />
* If WiFi is un-usable or often crashes when using an alternate OS, then it might because its WiFi firmware is not appropriate for the WiFi chip in the Pinebook Pro. Try the latest firmware patch from [https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm]<br />
* After re-enabling WiFi via the privacy switch, you have to reboot to restore function. There is a work around for the default Debian, (and may work with others);<br />
&nbsp; &nbsp; &nbsp; &nbsp; <code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.dwmmc'</code><br />
* On extremely rare occasions, the WiFi antenna connection is loose. To fix, simply open up the bottom, re-connect the WiFi antenna cable. This may show up as any of the following symptoms:<br />
** Can't connect to any network, but the network manager software sees the WiFi device, (so it has not been disabled by the Privacy Switch)<br />
** Very limited range, meaning you can make a connection if the Pinebook Pro is next to the WiFi router. But not the next room.<br />
** Unreliable connections, that are also limited by range.<br />
<br />
== Bluetooth issues ==<br />
<br />
* When connecting a Bluetooth device, such as a Bluetooth mouse, it does not automatically re-connect on re-boot. In the Bluetooth connection GUI, there is a yellow star for re-connect on boot. Use that button to enable a persistent connection. It can be changed back later.<br />
* Bluetooth-attached speakers or headset require the <b>pulseaudio-module-bluetooth</b> package. If not already installed, it can be installed with a package manager or using the following:<br />
<pre>sudo apt-get install pulseaudio-module-bluetooth</pre><br />
* When using Bluetooth-attached speakers or headset and 2.4Ghz WiFi at the same time, you may experience stuttering of the audio. One solution is to use 5Ghz WiFi if you can. Or you may try using a different 2.4Ghz channel, perhaps channel 1 or the top channel, (11 in the USA, or 13/14 in some other countries).<br />
<br />
= Sound issues =<br />
<br />
* Many reports of no sound are due to the OS, incorrect settings, or other software problems (eg. PulseAudio). So first test to see if it is a software or hardware problem, by trying another OS via SD card. (For example, if Debian is installed on the eMMC, try Ubuntu on SD.) <br />
* If you cannot get sound from the headphone jack, but can get sound from the speakers, then the headphone / UART console switch may be set to the UART mode. You can open the back and check the position of the switch. If set to UART mode, switch it to headphone mode. See the parts layout for the location and correct position of the switch.<br />
* When using the USB C alternate DisplayPort mode, it is possible that the audio has been re-directed through this path. If your monitor has speakers, see if they work.<br />
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/asound.state manjaro-arm/pinebookpro-post-install /var/lib/alsa/asound.state] for some ALSA tweaks.<br />
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-audio manjaro-arm/pinebookpro-audio] for how to handle 3.5mm jack plug/unplug events with ACPID.<br />
* Serveral users have reported that one internal speaker had reversed polarity. Thus, sound from the speakers is like an echo effect.<br />
** Their is a software fix using alsamixer and then enable either "R invert" or "L invert", however, now the headphones have incorrect audio.<br />
** The permanent fix is to re-wire one speaker, though this requires soldering small wires.<br />
* Sound playback may be affected by the "mirroring" between the right and left channels, which results in distorted sound image. The root cause is the [https://linux.die.net/man/1/alsamixer ALSA mixer] setting named "DAC Stereo Enhancement", which needs to be changed to 0% to fix this issue. Please see [https://forum.pine64.org/showthread.php?tid=12631&pid=87372#pid87372 this forum post] for further information.<br />
<br />
= NVMe SSD issues =<br />
<br />
Many PineBook Pro users have reported issues with NVMe SSD drives, including random Linux lockups and crashes. Some of these issues are related to the [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 RK3399's errata] that disables Gen2 (5&nbsp;GT/s) speed for the PCI Express link used by the NVMe SSD, reducing it down to Gen1 speed (2.5&nbsp;GT/s). However, as of December 17, 2020, Linux distributions that use mainline Linux kernel still configure the PCI Express link to run at Gen2 speed, which requires [https://forum.pine64.org/showthread.php?tid=11683 manual reconfiguration] to Gen1 speed in case system instability is experienced. See also this [https://patchwork.kernel.org/project/linux-rockchip/patch/20200423150510.6216-1-pgwipeout@gmail.com/ related discussion]. NOTE: This issue seems to have been [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=642fb2795290 fixed] in mainline 5.12. It has been tested on Manjaro ARM and seems to work with no modifications.<br />
<br />
Some PineBook Pro users have reported issues with the default settings for the APST (Autonomous Powe State Transition) power saving, which cause an NVMe drive to disappear from the system or lock up after a certain period of time. Please see [https://forum.pine64.org/showthread.php?tid=11337&pid=87711#pid87711 this forum thread] for further information.<br />
<br />
= Keyboard and trackpad =<br />
<br />
== Keys not registering / missing keys when typing ==<br />
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.<br />
<br />
Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.<br />
<br />
A [[Pinebook_Pro#Trackpad|firmware update]] has been released to address this.<br />
<br />
== Key mapping ==<br />
* See this [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb /etc/udev/hwdb.d/10-usb-kbd.hwdb] for some key mapping tweaks<br />
<br />
== Pinebook Pro gets stuck after first reboot in Trackpad Firmware Update ==<br />
This refers to the firmware update shown here:<br />
https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater#update-all-firmwares<br />
* If the system is not responding after the 1st reboot, it might be easiest to do a system restore or boot an sdcard-only OS, and follow up by running the second step of the trackpad firmware update with a USB keyboard and mouse plugged in<br />
* System restore https://forum.pine64.org/showthread.php?tid=8229<br />
* Firmware update https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater#update-all-firmwares<br />
<br />
== ANSI Fn + F keys wrong for F9, F10, F11 and F12 ==<br />
<br />
There appears to be a minor firmware issue for ANSI keyboard models of the Pinebook Pro. Some discussion and fixes have been proposed;<br />
* Discussion thread [https://forum.pine64.org/showthread.php?tid=8744&pid=57678#pid57678 Fn + F keys screwy for F9, F10, F11 and F12]<br />
* Proposed fix [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater/issues/14#issuecomment-576825396 (ANSI) Fn + F(9-12) has wrong assignment after firmware update #14]<br />
<br />
= USB docks & USB C alternate mode video =<br />
<br />
The Pinebook Pro uses the RK3399 SoC (System on a Chip). It supports a video pass through mode on the USB C port using DisplayPort alternate mode. This DisplayPort output comes from the same GPU used to display the built-in LCD. <br />
<br />
Here are some selection criteria for successfully using the USB C alternate mode for video:<br />
* The device must use USB C alternate mode DisplayPort. Not USB C alternate mode HDMI, or other.<br />
* The device can have a HDMI, DVI, or VGA connector, if it uses an active translater.<br />
* If USB 3 is also desired from a USB dock, the maximum resolution, frame rate and pixel depth is reduced to half the bandwidth. For example, 4K @ 30hz instead of 60hz.<br />
* USB docks that also use USB C alternate mode DisplayPort will always have USB 2 available, (480Mbps, half-duplex).<br />
<br />
=Screen=<br />
<br />
Also see above about external screen using USB-C adaptor<br />
<br />
== After changing builtin LCD resolution, blank screen ==<br />
Some people find that the text or icons are too small, so they attempt to change the resolution of the built-in display. Afterwards, the display is blank. <br />
Use the following to fix when logged into a text console as yourself, pressing Control-Alt-F1 through F6. After listing the resolutions, select the native resolution, (1920x1080 aka 1080p).<br />
<br />
<pre>export DISPLAY=:0.0<br />
xrandr -q<br />
xrandr -s [resolution]</pre><br />
<br />
Once the screen resolution is restored, try using the software settings to configure the desired screen scaling.<br />
<br />
If the above fix did not work, you can try this:<br />
* Using a text console, (Control-Alt-F1), login with your normal user ID<br />
* Edit the file <code>nano ~/.config/monitors.xml</code><br />
* Change the "width" value to "1920"<br />
* Change the "height" value to "1080"<br />
* If there is more than one monitor configuration listed, edit that one too. Be careful to make no other changes. If needed, exit without saving and re-edit.<br />
* Save the file and exit.<br />
* Login using the GUI and test<br />
* If you are still loggied in via the GUI, you will have to reboot using <code>sudo shutdown -r now</code>. After the reboot, you should be able to login to the GUI login and have the resolution back to normal.<br />
<br />
After restoring the usability of your Pinebook Pro's graphical screen, also see [[Pinebook Pro#Improving readability|this section]] on improving readability and usability.<br />
<br />
=Outer Shell=<br />
<br />
== Cracks in the plastic ==<br />
There have been multiple reports of cracks in the plastic keyboard and trackpad part of the case. These are generally near:<br />
* Hinges<br />
* USB ports<br />
* Top side, around the corners<br />
<br />
This seems to apply to the first batches in 2019. Later versions of the keyboard and trackpad have used better plastic. With replacements now in the Pine64 Store, it's possible to simply order a replacement.<br />
<br />
There have been a few reports of cracks in the plastic around the LCD display, but these appear to be less common. There are replacement LCDs with top cases available in the Pine64 Store.<br />
<br />
[[Category:PineBook Pro]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Switching_your_PineTime_between_InfiniTime_and_Wasp-os&diff=10783Switching your PineTime between InfiniTime and Wasp-os2021-06-19T07:36:51Z<p>JerseyDevil: category</p>
<hr />
<div>[[File:Flash-reloader-mcuboot.jpg|600px|thumb|right|Flashing <code>reloader-mcuboot.zip</code>]]<br />
[[File:Flash-micropython.jpg|400px|thumb|right|Flashing <code>micropython.zip</code>]]<br />
== Introduction ==<br />
Both Infinitime and Wasp-os are very cool OS'es for the [[PineTime]] and many people will want to try both. This is possible, even with a sealed device!<br />
<br />
Both devices use the same Nordic (legacy) DFU protocol for updating firmware over the air. But the BLE stack and the bootloaders for both are different. That's why we need to use the [https://github.com/daniel-thompson/wasp-reloader reloader]. However, instructions you find elsewhere (including [https://www.youtube.com/watch?v=lPasAt1LJmo Daniel Thompsons video]) are somewhat outdated.<br />
<br />
Flashing can be done with any of<br />
* nRF Connect for Mobile ([https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp Android], [https://apps.apple.com/us/app/nrf-connect-bluetooth-app/id1054362403 iOS])<br />
* [https://www.gadgetbridge.org GadgetBridge] (Android >= 4.4)<br />
* [https://github.com/piggz/harbour-amazfish Amazfish] (SailfishOS and Linux)<br />
* [https://github.com/alexr4535/siglo Siglo] (Linux desktop and Pinephone) (Use the 'Manual OTA File' option)<br />
* [https://github.com/ZephyrLabs/PinetimeFlasher PinetimeFlasher] (Windows)<br />
* ota-dfu-python (Linux CLI) which is included in sources of both Infinitime and Wasp-os<br />
** <code>InfiniTime/bootloader/ota-dfu-python/dfu.py</code><br />
** <code>wasp-os/tools/ota-dfu-python/dfu.py</code><br />
<br />
This guide has been last updated for Infinitime 1.1.0 and Wasp-os 0.4<br />
<br />
== InfiniTime => Wasp-os ==<br />
<br />
All the zips you need can be found on the [https://github.com/daniel-thompson/wasp-os/releases/ Wasp-os Releases] page, for example in [https://github.com/daniel-thompson/wasp-os/releases/download/v0.4/wasp-os-0.4.tar.gz wasp-os-0.4.tar.gz].<br />
<br />
* Make sure the watch is running Infinitime and can be found by your companion device (PC, phone, etc).<br />
* First we need to flash the reloader, with the wasp-os bootloader as payload. To do this, flash: <br><code>wasp-os-0.4/build-pinetime/reloader-mcuboot.zip</code><br />
* After flashing, it will boot using the Infinitime bootloader (green large pine cone), then it'll hang for a few seconds, then it'll show the reloader animation (blue smaller pine cone), and then it'll boot the wasp-os bootloader.<br />
* Make sure the watch is on the screen with the pine cone and arrow. If it is in a bootloop instead, then reboot the watch by holding the button until the arrow appears.<br />
* Now you can flash micropython with wasp-os: <br><code>wasp-os-0.4/build-pinetime/micropython.zip</code><br />
* Wasp-os should now boot. Enjoy!<br />
<br />
== Wasp-os => InfiniTime ==<br />
[[File:Flash-reloader-infinitime-recovery.jpg|500px|thumb|right|Flashing <code>reloader-infinitime-recovery-0.14.1.zip.zip</code>]]<br />
[[File:Flash-infinitime.jpg|600px|thumb|right|Flashing <code>pinetime-mcuboot-app-dfu-1.1.0.zip.zip</code>]]<br />
<br />
The <code>reloader-factory.zip</code> are unfortunately broken in wasp-os 0.4, and very outdated in older releases. I do not recommend flashing these. Older InfiniTime versions have flaky BLE which makes upgrading from there very unreliable. Trying to create new zips containing any recent version of InfiniTime also fails, because it has grown too big to fit inside a zip together with the reloader and bootloader.<br />
<br />
Instead, I made my own containing just the [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 InfiniTime 0.14.1] [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/develop/README.md#recovery-firmware recovery firmware]. This allows you to flash any future release of InfiniTime without having to find a new reloader zip. Get the [https://github.com/Peetz0r/wasp-reloader/releases/tag/infinitime-0.14.1-recovery reloader zip here] and the [https://github.com/JF002/InfiniTime/releases latest Infinitime here].<br />
<br />
* Reboot the watch by holding the button until the pine cone arrow appears.<br />
* Flash the reloader zip: <br><code>reloader-infinitime-recovery-0.14.1.zip</code><br />
* After flashing, the reloader will run (blue smaller pine cone), then it'll boot the InfiniTime bootloader (large pine cone) will run.<br />
* Boot the watch into recovery mode by holding the button until the pine cone turns red. It'll boot again (large pine cone will turn green) and then the InfiniTime loo will appear.<br />
* You can now flash InfiniTime 1.1.0 (or any other version): <br><code>pinetime-mcuboot-app-dfu-1.1.0.zip</code><br />
* InfiniTime should now boot. Enjoy!<br />
<br />
<br />
[[Category:PineTime]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PinePhone_Installation_Instructions&diff=10782PinePhone Installation Instructions2021-06-19T07:33:50Z<p>JerseyDevil: category</p>
<hr />
<div>This section has generic installation instructions. Please see the [[PinePhone Software Releases]] section for specific installation instructions for each distribution.<br />
<br />
== Boot priority ==<br />
<br />
The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.<br />
<br />
== Installation to the microSD ==<br />
<br />
To install an image to the microSD card:<br />
<br />
# Download your chosen image from [[PinePhone Software Releases]]<br />
# Extract the compressed file<br />
# Write the image to your SD card, see below<br />
# Plug SD card into phone<br />
# Boot phone<br />
<br />
If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|the NOOB guide]], then return to this page.<br />
<br />
=== Flashing the microSD ===<br />
==== Using dd ====<br />
Make sure to select the correct device using <code>lsblk</code>. Then run <code>dd</code> with the correct device:<br />
<br />
<pre><br />
sudo dd if=pine.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync<br />
</pre><br />
<br />
==== Using bmaptool ====<br />
Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device:<br />
<br />
Download the .img.xz and the .img.bmap files, then run <code>bmaptool copy --bmap image.bmap image.xz /dev/[DEVICE]</code>. This takes around 2.5 minutes to flash a 4 Gb file.<br />
<br />
==== Using graphical tools ====<br />
GUI applications such as Etcher and GNOME Disks can be used to flash the MicroSD too.<br />
<br />
== Installation to the eMMC ==<br />
=== Using JumpDrive ===<br />
<br />
[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]<br />
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.<br />
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.<br />
The process of flashing an OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a SD card. You can use the <i>dd</i> command or a utility such as Etcher or Gnome Disks, etc.<br />
<br />
Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].<br />
<br />
# Download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# Flash the Jumpdrive image to a micro SD card<br />
# Boot the PinePhone from the Jumpdrive micro SD card<br />
# Connect the PinePhone to your computer using USB-A -> USB-C cable<br />
# Flash the exposed PinePhone drive (e.g. /dev/mm..., check for the right device in dmesg, GNOME disks, or similar, and make sure it's unmounted) with your chosen OS image<br />
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# The process is now finished, and you can boot from eMMC<br />
<br />
The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice. Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!<br />
<br />
=== From the booted microSD OS ===<br />
<br />
# Flash an OS to the SD card (and optionally resize the partition, see below)<br />
# Insert SD card and boot the phone<br />
# Download the desired OS' image on the booted OS or transfer it to the SD card<br />
# Extract the image file if it is archived<br />
# Flash the image file to eMMC using <code>dd if=new-pinephone-image.img of=/dev/mmcblkX bs=1M status=progress conv=fsync</code> where X is the number label of the eMMC (of the disk, not the partition!). Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. <br />
# Turn off phone, remove SD card and then turn on the phone.<br />
<br />
=== From the booted microSD OS (risky) ===<br />
<br />
{{Warning|This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption.}}<br />
<br />
# Prepare a new SD card, flash desired OS to the SD card<br />
# Boot the phone with your new SD card image<br />
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.<br />
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.<br />
# Open terminal and resize partition to fill up entire disk (see below).<br />
<br />
=== SD to eMMC via installer ===<br />
<br />
postmarketOS installer images booted from SD card will simply ask the user, if they want to install to eMMC. The feature lives in the distro-agnostic calamares-extensions repository (see [https://github.com/calamares/calamares-extensions/pull/7 calamares-extensions#7]), so other distributions might adopt this in the future.<br />
<br />
== Resize partition to fit disk space ==<br />
<br />
{{Hint|Many OSes already include a script, which is resizing the partition on first boot, where this step is not required.}}<br />
<br />
Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.<br />
<br />
=== Resize SD card's partition using computer ===<br />
<br />
For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image. To do the flashing you have two options:<br />
<br />
====Using Growpart ====<br />
<br />
Install <i>growpart</i> and run:<br />
growpart /dev/mmcblkX Y<br />
resize2fs /dev/mmcblkXpY<br />
where X is the storage device and Y is the partition number (viewable from <code>lsblk</code>).<br />
<br />
If you get any errors about missing or unknown commands, use <code>apt-cache search</code> to find and install the needed software. Also don't forget to use <code>sudo</code>.<br />
<br />
====Using Parted ====<br />
<br />
Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.<br />
<br />
sudo parted /dev/<your_sd_card_device><br />
(parted) resizepart 2 100%<br />
(parted) quit<br />
sudo resize /dev/<the_second_sd_card_PARTITION><br />
<br />
=== Resize from within PinePhone ===<br />
<br />
eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. If you booted from the SD card, you can follow the above guidelines on how to resize from a computer. <br />
<br />
SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order - you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.<br />
<br />
== Reuse SD card for data storage on system booting from eMMC==<br />
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.<br />
<br />
This can be done as follows on any linux system:<br />
lsblk<br />
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0<br />
then<br />
sudo dd if=/dev/zero of=/dev/<your_sd_card_device> bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card.<br />
<br />
== Web resources ==<br />
<br />
* [https://www.youtube.com/watch?v=7HMkU43P9hw Youtube video on how to flash OS images on the Pinephone (SD or eMMC) by Tech Pills]<br />
* [https://www.youtube.com/watch?v=u65dofYFAPY Youtube video on How to install different OSes On the PinePhone plus an Mobian overview by Elatronion]<br />
<br />
<br />
[[Category:PinePhone]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Getting_started&diff=10781Getting started2021-06-19T07:19:50Z<p>JerseyDevil: category</p>
<hr />
<div>== Setting Up Your device - What You’ll Need to Get Started ==<br />
<br />
You will need the following to get started with using your PINE A64(+), SOPine/PINE A64-LTS, Pinebook or ROCK64 board:<br />
* Windows / Linux PC or MAC with a MicroSD Card Reader and connection to the Internet.<br />
* Power Supply<br />
:: For PINE A64(+): 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.<br />
:: For SOPine/PINE A64-LTS: Power Supply (PSU) with 3.5mm OD/1.5mm ID barrel DC Jack. Please make sure to use a PSU rated at +5V @2A.<br />
:: For Pinebook and ROCK64: Power Supply (PSU) with 3.5mm OD/1.5mm ID barrel DC Jack. Please make sure to use a PSU rated at +5V @3A.<br />
* MicroSD card (8GB or higher capacity) rated 'class 10' or better.<br />
* HDMI cable (unless you wish to run headless / without a monitor). On '''A64 Devices''' 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].<br />
* Input device(s) such as: keyboard, mouse, remote, pointer, etc.<br />
<br />
== Step-by-Step Instructions for Flashing MicroSD Cards ==<br />
<br />
{{Note|'''Caution!''' Handle the Pine64 Single Board Computers' PCBs with care. Always hold bare boards by the edges and make sure to wear an anti-static wrist strap. Touching components on the front and back of the boards can result in an ESD discharge that may cause damage to the electronics. Avoid placing bare boards on materials such as carpets, plastics or other surfaces prone to electrostatic build-up}}<br />
<br />
<br />
'''Begin by imaging the OS of your choice'''<br />
<br />
The process of flashing PINE64 OS images to micro SD on your Windows, Linux or OSX device is the same for all devices. You will require a quality microSD card (8GB or greater; class 10 or faster). There are many [https://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 [https://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]. Yet another overview of various options [https://www.raymond.cc/blog/test-and-detect-fake-or-counterfeit-usb-flash-drives-bought-from-ebay-with-h2testw/ Test and Detect Fake Cards]<br />
<br />
Please refer to the relevant section below for instructions on how to image your microSD card:<br />
* [[#Imaging microSD on Windows 7/8/8.1/10|Imaging microSD on Windows 7/8/8.1/10]]<br />
* [[#Imaging microSD on Apple OSX|Imaging microSD on Apple OSX]]<br />
* [[#Imaging microSD on Linux|Imaging microSD on Linux]]<br />
<br />
Having successfully imaged your microSD card, insert it into the microSD slot.<br />
<br />
<br />
'''Plug in the HDMI Cable, Ethernet Cable and Peripherals to your PINE64 SBC'''<br />
<br />
Unless you are planning on running your board 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. <br />
<br />
<br />
'''Apply Power to Your Board'''<br />
<br />
Once you have imaged your microSD and plugged everything in, you are ready to apply power to the PINE64 Single Board Computer. You'll need a good quality 5 Volt, 2 Amp PSU. Using a good quality PSU 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 PINE64 Single Board Computer and may render it inoperative.<br />
<br />
For PINE A64(+) board, 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 [https://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.<br />
<br />
Having completed the steps outlined above the PINE64 Single Board Computer will begin to boot. The onboard power-on LEDs will come on and Ethernet port LEDs will start to blink if you have an Ethernet cable plugged in. <br />
<br />
<br />
----<br />
<br />
=== Imaging microSD on Windows 7/8/8.1/10 ===<br />
<br />
You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:<br />
* A compression utility (used to unarchive the OS image). We recommend you use [https://www.7-zip.org/download.html 7zip].<br />
* A disk image utility (used to flash the .img to your SD card). We recommend you use either the [https://etcher.io/ Etcher] or [https://sourceforge.net/projects/win32diskimager/ Win32Imager] utility.<br />
<br />
'''Optional for Allwinner A64 SoC based boards'''<br />
* 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].<br />
<br />
<br />
'''Downloading and extracting OS image(s)'''<br />
<br />
You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page. <br />
Images designated ‘DD’ need to be flashed using Etcher or Win32imager, whilst images labelled ‘Phoenix Card Image’ require the Phoenix Card utility.<br />
<br />
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.<br />
<br />
<br />
'''Imaging the microSD card (DD)'''<br />
<br />
* 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.<br />
<br />
* 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. {{warning|'''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}<br />
<br />
* 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.<br />
<br />
<br />
'''Imaging using Phoenix Card (applicable only to Allwinner A64 SoC based boards)'''<br />
<br />
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:<br />
<br />
* 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.<br />
<br />
* 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. {{warning|'''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}<br />
<br />
* 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.<br />
<br />
<br />
----<br />
<br />
=== Imaging microSD on Apple OSX ===<br />
<br />
You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:<br />
* A compression Utility (used to unarchive the OS image). We recommend you use [https://www.7-zip.org/download.html 7Zip].<br />
* A disk image utility (used to flash the .img to your SD card in GUI). We recommend you use [https://mac.softpedia.com/get/Utilities/ApplePi-Baker.shtml#download ApplePi Baker] or [https://etcher.io/ Etcher].<br />
{{hint|'''N.B.''' Phoenix Card utility and images are NOT available on Apple OSX.}}<br />
<br />
'''Downloading and extracting OS image(s)'''<br />
<br />
You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page. On OSX you can only use images designated as ‘DD’.<br />
<br />
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.<br />
<br />
<br />
'''Imaging the microSD card (GUI)'''<br />
<br />
* 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.<br />
<br />
* 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. {{warning|'''N.B.''' Pay close attention to the selected drive – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}<br />
<br />
* 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.<br />
<br />
<br />
'''Imaging from Terminal'''<br />
<br />
{{note|'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.}}<br />
<br />
* 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.<br />
<br />
* Open up your terminal and navigate to the directory where you unarchived your OS image.<br />
<br />
* Before you start writing to the card, you will have to identify your microSD card. Type: <code>diskutil list</code> 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):<br />
<br />
::<code>diskutil unmountDisk /dev/diskX</code><br />
<br />
::<code>sudo dd if=pine64-image-name.img of=/dev/disk2 bs=1M</code><br />
<br />
* Wait patiently for the process to complete. Be sure to eject/remove your SD card safely from your Mac.<br />
<br />
<br />
----<br />
<br />
=== Imaging microSD on Linux ===<br />
<br />
You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:<br />
* A compression Utility (used to unarchive the OS image). We recommend you use [https://apps.kde.org/en/ark Ark].<br />
* A disk image utility (used to flash 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.<br />
{{hint|'''N.B.''' Phoenix Card utility and images are NOT available on Linux.}}<br />
<br />
'''Downloading and extracting OS image(s)'''<br />
<br />
You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page. On Linux you can only use images designated as ‘DD’.<br />
<br />
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.<br />
<br />
<br />
'''Imaging the microSD card (GUI)'''<br />
<br />
* 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.<br />
<br />
* 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]).<br />
<br />
* 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. {{warning|'''N.B.''' Pay close attention to the selected drive – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}<br />
<br />
* 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).<br />
<br />
* 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.<br />
<br />
<br />
'''Imaging from Terminal'''<br />
<br />
::{{note|'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.}}<br />
<br />
* 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.<br />
* Open up your terminal and navigate to the directory where you unarchived your OS image. e.g. <code>cd Download</code><br />
* Before you start writing to the card, you will have to identify your microSD card.<br />
<br />
* Type: <code>lsblk</code> and pay attention to the listed disks. Disks will appear as ''/dev/mmcblk0 /dev/mmcblk1'' etc. <br />
::{{note|'''Hint''': the drive you currently have booted from has the <code>/</code> at the end of the line. This is the wrong drive. Look at the drive that matches your microSD card’s size.}}<br />
<br />
* Now you are ready to write the image to the microSD card using this command: (replace the pine.img file with your image and mmcblkX with the correct device for the microSD card)<br />
::<code>sudo umount /dev/mmcblkX</code><br />
::<code>sudo dd if=pine.img of=/dev/mmcblkX bs=1M status=progress conv=fsync</code><br />
<br />
* Wait patiently for the process to complete.<br />
* use the command <code>sync</code> to ensure everything is written to the microSD card.<br />
* The card is ready to boot <br />
<br />
(sometimes this process fails and your microSD card can't boot, one way of fixing this is just to repeat the same thing, you can also try a different microSD card)<br />
<br />
== Instructions to Flashing eMMC Modules ==<br />
<br />
All PINE64 devices - with the '''notable exception of the original Pine A64(+) SBC''' - support eMMC modules as an alternative boot and storage solution to micro SD cards.<br />
An eMMC module can be purchased for your device(s) from the [https://pine64.com/?post_type=product PINE64 store]. The only PINE64 device that ships with an eMMC module by default is the Pinebook.<br />
<br />
The available modules come in three different capacities: 16Gb, 32Gb, 64Gb and 128Gb<br />
<br />
There are a few ways to flash eMMC modules with the desired OS image. The following sections are a summary of the processes involved in flashing the OS image of your choice to the eMMC module. <br />
<br />
<br />
----<br />
<br />
=== Flashing Using the USB-to-eMMC Adapter (Preferred Way) ===<br />
<br />
A USB-to-eMMC adapter is available from purchase from the [https://pine64.com/product/usb-adapter-for-emmc-module/ PINE64 Store] making it easy to mount the eMMC module as a volume in your Windows, Mac OS or Linux computer. The eMMC can hence be flashed directly from your computer with any image similarly to a micro SD card.<br />
<br />
'''This installation method works for all devices that support eMMC modules regardless of the chipset''' and it is therefore the preferred way of flashing OS images to eMMC. All available OS images for your device can be installed on the eMMC module this way. <br />
<br />
*This process of flashing an OS image to eMMC is '''literally identical to imaging micro SD cards''', so please read [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Step-by-Step Instructions to Flashing Micro SD Cards]] before you begin. <br />
<br />
For this method you will need the following: <br />
<br />
*A Windows, Linux or Mac OS computer<br />
*A PINE64 eMMC module<br />
*The PINE64 USB-to-eMMC adapter<br />
<br />
<br />
'''Flashing eMMC using the adapter'''<br />
<br />
*Insert the the eMMC module into the USB adaptor and plug it into your Windows, Linux or Mac OS computer. It should mount as a regular USB drive and show up in your file manager. <br />
*If you are using Linux or Mac OS you can either use the dd terminal command or a GUI utility such as [https://etcher.io/ Etcher] to flash the chosen OS Image to eMMC. <br />
*If you are using a Windows machine use [https://etcher.io/ Etcher] or [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager] to flash the OS Image to the eMMC module. <br />
<br />
Once the image has been flashed using your preferred method safely dismount the USB adaptor in your system and unplug it from your computer. Your eMMC is now ready to boot and can be inserted into the eMMC socket on your PINE64 device.<br />
<br />
<br />
----<br />
<br />
=== Flashing to eMMC from a SD Boot ===<br />
<br />
Some of the available Linux images for Allwinner A64 devices recognise eMMC modules as mounted storage when the device is booted from a micro SD card. This is true for all recent releases of [https://github.com/ayufan-pine64/linux-build/releases ayufan's Linux images]. In result it is possible to flash an OS image to eMMC using the DD command in terminal or the Disks GUI utility included with the Mate desktop. <br />
<br />
There are '''two ways''' in which an OS image can be flashed from within a micro SD boot: <br />
*Via a script called Pine64_install_to_eMMC.sh found in ''/usr/local/sbin''. This script will install an Ubuntu Mate OS installation (identical to the on running on the SD) to the eMMC module. To execute the script navigate to its location in the terminal and type <code>sudo ./Pine64_install_to_eMMC.sh</code>. Follow the instructions. <br />
<br />
*By manually downloading and flashing a OS image for your device using DD or the Disk GUI. This way of flashing an OS image to the eMMC is identical to that used on a Linux computer (e.g. for flashing an OS image to a SD card). For more information on how the process works please see the detailed guide on [[NOOB#Imaging_microSD_on_Linux|imaging OS images to SD card on Linux]]. <br />
<br />
For the latter of the two methods here is a summary of the process: <br />
*Flash an OS image which recognizes eMMC as mounted storage to a micro SD card. For details on how to flash a micro SD card see [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|section 3]] <br />
*Insert both the micro SD and eMMC module into your device and power it on.<br />
*Once the PINE64 device boots from micro SD, you cannot flash the contents of the micro SD card to the eMMC while you are running from the micro SD so you will actually use this session to download an OS image to flash to the eMMC. Depending on the distribution this may be the same image you just flashed to the micro SD card and booted from.<br />
*Once the OS image downloads check in terminal or in Disks utility the eMMC's mounting location and unmount all but "/". Example command to show disks and mounts:<br />
::<blockquote><code>$ lsblk</code></blockquote><br />
*Use the DD command or Disks utility to flash the downloaded image to the eMMC module. Note your output device may be mmcblk1 or mmcblk2, use the command above to verify the correct one. Example DD command:<br />
::<blockquote><code>$ xzcat imagename.img.xz | sudo dd of=/dev/mmcblk1 bs=1M status=progress conv=fsync</code></blockquote><br />
*Once the flashing process is completed power down your device and remove the micro SD card. You should now be able to power your device back up and it will boot the image flashed to the eMMC module.<br />
<br />
<br />
----<br />
<br />
=== Flashing to eMMC using FEL (Allwinner A64 Devices Only) ===<br />
<br />
Under particular circumstances it may prove difficult to rely on a SD card to flash an OS image to an Allwinner A64 device. In such instances OS images can be directly flashed by means of entering into FEL mode. FEL is a low-level subroutine in the BootROM, and the process of enabling FEL differs from one device to another. To learn more about FEL please refer to the [https://linux-sunxi.org/FEL SUNXI Wiki section] dedicated to the subject. <br />
<br />
The process of flashing via FEL is more complex than utilising a micro SD and is therefore '''better suited for proficient and advanced users'''. <br />
<br />
For the process of flashing an image to the eMMC on a device in FEL mode you will need: <br />
*A computer running Mac OS or Linux<br />
*An OTG USB A-to-A cable <br />
<br />
To enter FEL you will need to: <br />
*On the Pinebook, power down the Pinebook and remove the PSU, unscrew the bottom of the case and press down the FEL button on the PCB (REF). Plug in the OTG USB A-to-A cord to your computer and the OTG USB port on the Pinebook (on the right facing an open case). Reinsert the PSU cord and press the power button with the FEL button pressed down. Release the FEL button after 3 seconds. <br />
*On the Pine A64(+) power down the board and remove the micro SD card and power cord. Plug in the OTG USB A-to-A cord to your computer and the OTG USB port on the Pine A64 (+) and SoPine (top port). Power on the device and immediately after insert a micro SD card [https://app.box.com/s/s3m7rb5zfe0jkwqhaiy1zytqq3436fqs with FEL code].<br />
<br />
You can check if your device entered FEL mode using ''lsusb'' command in terminal. It should be listed as a device on the USB Bus. <br />
<br />
The next step is to mount your device so that your computer recognizes the eMMC as mass storage (UMS). A script called boot-tools streamlining this process is available '''thanks to ayufan''' on [https://github.com/ayufan-pine64/boot-tools his github]. Follow his instructions and in terminal perform the following steps: <br />
<br />
::<code>git clone <nowiki>https://github.com/ayufan-pine64/boot-tools.git</nowiki></code><br />
<br />
::<code>cd boot-tools</code><br />
<br />
::<code>make pinebook_ums</code><br />
<br />
or<br />
<br />
::<code>make pine64_ums</code><br />
<br />
Once your device mounts as UMS it will appear in your file manager. In CLI you can check if the storage is listed using ''fdisk -l''. <br />
<br />
This process of flashing an OS image to eMMC with the device in FEL mode and mounted as UMS is '''literally identical to imaging micro SD cards''', so please read [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Step-by-Step Instructions to Flashing Micro SD Cards]] and follow the procedure. You can use DD or Disks/ Disk Utility to flash the OS image directly to your device's eMMC. <br />
<br />
Once the flashing process is completed, power down your device, remove the A-to-A USB OTG cable and after reapply power to boot your device from eMMC.<br />
<br />
<br />
----<br />
<br />
=== Flashing to eMMC using Rockchip Tools (Rock64 Only) ===<br />
<br />
Rockchip has a different boot hierarchy to Allwinner's devices making it much more difficult to flash OS images using the micro SD-to-eMMC scheme used on A64. There are, however, flashing tools that make it possible to flash directly to eMMC on a Rock64 in loader and MarkROM modes. <br />
<br />
To flash to the eMMC module using these tools you will need the following: <br />
*A Windows, Mac OS or Linux computer<br />
*An A-to-A USB cable <br />
*The Rock64 board with the eMMC module inserted into the socket<br />
<br />
<br />
'''Using Windows 7/8.1/10 ''' <br />
You will need to download the [https://github.com/rockchip-linux/tools/tree/master/windows DriverAssistant aka Rockchip driver] as well as the [https://github.com/rockchip-linux/tools/tree/master/windows AndroidTool_Release] used for flashing OS images. Having completed the downloads extract both archives.The Rockchip driver needs to be installed prior to using the AndroidTool utility. <br />
<br />
Having installed the driver and flashing utility, follow these steps:<br />
*Make sure that eMMC is inserted into the slot on the Rock64<br />
*Place a jumper / short out the eMMC pins on the board (consult [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf this PDF document] for more details.<br />
*Insert one end of the A-to-A cable into your Windows PC and the other into your Rock64 OTG USB port (top)<br />
*Inset the power cord into the Rock64<br />
*Start AndroidTool; make sure that it reports 'Found One Maskrom Device' (if it does not recognise your device, please repeat previous steps)<br />
*Select either the latest Stock Android build or ayufan's Android TV build with the suffic -update. Download and the extract the chosen image. <br />
*In AndroidTool press the firmware tab and navigate to where you extracted the OS image and select it. <br />
*Press the upgrade tab. You will be prompted when the flashing process is completed. <br />
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC. <br />
<br />
<br />
'''Using Linux or Mac OS'''<br />
<br />
*Make sure that eMMC is inserted into the slot on the Rock64<br />
*Download latest stable or pre-release (to be used at own risk) Android TV OS image from [https://github.com/ayufan-rock64/android-7.1/releases ayufan's github]. The image you wish to download is the one '''without a suffix'''; without -update or -raw in the OS image title. <br />
*In terminal, download rkflashtool following instructions on [https://github.com/ayufan-rock64/android-7.1/blob/master/README.md ayufan's github]<br />
*Extract the folder containing partitions of the OS image and place the script listed on ayufan's github in the folder<br />
*Hold down the recovery button on the board<br />
*Insert one end of the A-to-A cable into your Mac OS or Linux PC and the other into your Rock64 OTG USB port (top)<br />
*Inset the power cord into the Rock64<br />
*Check that your device is in loader mode by typing in the terminal <code>sudo rkflashtool n</code>. If rkflashtool doesn't detect the Rock64 please repeat last 3 steps <br />
*In terminal navigate to where you extracted the Android folder containing the OS partitions and the script and type <code>rkinstall</code>; this will install the community Android TV build to eMMC. <br />
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.<br />
<br />
<br />
----<br />
<br />
=== Flashing to eMMC Android 'Update' OS Images on Linux (Rock64 Only) ===<br />
<br />
It is possible to flash Android 'update' images to the Rock64 eMMC using a Linux PC. This process requires a tool called [https://www.haoyuelectronics.com/service/RK3066/tools/linux/Linux_Upgrade_Tool_v1.2.tar.gz Linux Upgrade Tool] and the full documentation of its functions can be found [https://www.hotmcu.com/wiki/Flashing_Firmware_Image_Files_Using_The_Rockchip_Tool#Using_Linux_Upgrade_Tool_to_flash_update.img here]. Make sure that you download v1.2 or newer, as older tools do not support the RK3328 used on the Rock64. <br />
<br />
To flash the eMMC module using this method you will need the following: <br />
*A Linux computer<br />
*An A-to-A USB cable <br />
*The Rock64 board with the eMMC module inserted into the socket<br />
<br />
Start by downloading an Android '''update''' image for the Rock64. Both PINE64 and Ayufan provide such images for the board - and they are clearly designated as such on both this WiKi's download section and on ayufan's github. For the purpose of this example, I'll use the ayufan's ATV community build: <br />
<br />
*Download latest stable or pre-release (to be used at own risk) Android TV OS image from [https://github.com/ayufan-rock64/android-7.1/releases ayufan's github]. The image you wish to download is the one '''with update suffix'''. You need to '''rename the downloaded image to update.img'''.<br />
*Download the [https://www.haoyuelectronics.com/service/RK3066/tools/linux/Linux_Upgrade_Tool_v1.2.tar.gz Linux Upgrade Tool] to your Linux PC and unarchived it. <br />
*Extract the archived update Android OS image somewhere where you will remember its path<br />
*Hold down the recovery button on the board<br />
*Insert one end of the A-to-A cable into your Mac OS or Linux PC and the other into your Rock64 OTG USB port (top)<br />
*Inset the power cord into the Rock64<br />
*In terminal, navigate to where you extracted Rockchip Update Tool and issue the following command substituting the correct path for where the Android Update OS Image is located:<br />
<br />
::<code>sudo ./upgrade_tool uf /path/to/update.img</code><br />
<br />
*Wait as the utility installs Android to eMMC on your Rock64. <br />
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.<br />
<br />
== Flashing u-boot to SPI Flash ==<br />
<br />
Some of PINE64 devices, such as the Rock64 and SOPine, are equipped with SPI Flash. This allows users to flash u-boot onto the SPI and boot from an external USB 2.0 or USB 3.0 SSD/HDD/thumb-drive, thereby forgoing use of eMMC or microSD card. <br />
<br />
To find out more about which images can used in conjunction for SPI booting please see [https://github.com/ayufan-rock64/ ayufan's github].<br />
<br />
Writing u-boot to SPI Flash can be achieved in two ways:<br />
<br />
=== Using a Stand-Alone Image to Write u-boot to SPI ===<br />
This may be the simplest method of flashing u-boot to SPI. Download a dedicated image labelled '''u-boot-flash-spi.img.xz''' from [https://github.com/ayufan-rock64/linux-u-boot/releases ayufan's github] and flash it to a microSD card, the same as you would with any OS image (to learn how to flash OS images to microSD please follow steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]].<br />
<br />
'''Having flashed the image follow these steps''': <br />
<br />
*Insert the SD into the ROCK64<br />
*Remove all other peripherals from the board <br />
*'''Make sure that the eMMC module is disconnected from the board'''<br />
*Apply power to the ROCK64<br />
*Wait (few seconds) until the the LEDs on the board will blink continually<br />
*Power off the board.<br />
<br />
The board is now ready to boot from USB 2.0/3.0 storage.<br />
<br />
=== Using a Script on Linux OS Images ===<br />
Most of recent (newer than 0.6.9) Linux OS images contain a script called '''rock64_write_spi_flash.sh''', which is found in ''/usr/local/sbin'' directory. To run the script you will first need to flash a Linux OS image to a micro SD card (to learn how to flash OS images to micro SD please following steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]]). Before proceeding '''make sure that the eMMC module is disconnected''' from the board. Once you have booted into Linux on your PINE64 device all you have to do is run the aforementioned script using this command: <br />
<br />
::<code>sudo ./rock64_write_spi_flash.sh</code><br />
<br />
Once the script finishes its operation, power off your board and remove the microSD card.<br />
The board is now ready to boot from USB 2.0/3.0 storage.<br />
<br />
=== Erasing and Rewriting SPI === <br />
There are two ways of removing u-boot from SPI. You can either download '''u-boot-flash-spi.img.xz''' from [https://github.com/ayufan-rock64/linux-u-boot/releases ayufan's github] or use a script found on Linux OS images titled:'''rock64_erase_spi_flash.sh'''. Follow the instructions in the previous sub-sections for the chosen method of removing u-boot from SPI; the instructions are are identical, as the process of erasing u-boot is the exact opposite of flashing it. <br />
<br />
{{hint|'''N.B.''' You can also erase SPI manually.}}<br />
To do so, you need to download mtd-utils. on Debian or Ubuntu follow these instructions:<br />
<br />
::<code>sudo apt-get install mtd-utils</code><br />
<br />
::<code>sudo flash_eraseall /dev/mtd0</code><br />
<br />
=== Booting an OS image from USB 2.0/3.0 Storage ===<br />
To boot an OS image from USB 2.0/3.0 Storage such as a SSD/HDD or a thumbdrive you first need to have u-boot written to your SPI flash. Please follow the instructions in the previous sub-sections to learn how to write u-boot to SPI on your PINE64 device. <br />
<br />
Once you have u-boot on your SPI, the process of booting is very similar to booting from microSD or eMMC.<br />
*Download one of the supported OS images for your PINE64 device<br />
*Flash the OS image to your USB 2.0/USB 3.0 storage device (to learn how to flash OS images please following steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]] The instructions are identical for all types of storage, including USB 2.0/USB 3.0 HDDs and thumb-drives.) <br />
*Insert the USB storage device with the flashed OS image into one of the USB ports on your PINE64 device<br />
*Apply power<br />
<br />
If you have followed all the steps correctly, the board should boot from your USB 2.0/3.0 storage device.<br />
<br />
== Troubleshooting Your Device ==<br />
<br />
A number of things can prevent the PINE64 board from booting up properly. The most common culprits of a failed boot are: (to find out more click [https://forum.pine64.org/showthread.php?tid=514 here])<br />
<br />
* Subpar or counterfeit microSD card<br />
* Subpar Power Supply<br />
* High resistance (thin) or a very long microUSB cable<br />
* Failed imaging of the microSD card or eMMC module<br />
<br />
Make sure to have the newest version of the OS image your are running. On Allwinner A64 devices running Linux you can update the kernel and uboot using scripts located in the following directory: /usr/local/sbin<br />
<br />
* To navigate to the directory type (in terminal): <code>cd /usr/local/sbin</code><br />
* You list all the available scripts by typing (in terminal): <code>ls</code><br />
* To run the script required update script run the following command: <code>sudo ./update_script.sh</code> (substitute the relevant update script for <code>update_script</code>)<br />
<br />
'''Troubleshooting Step by Step'''<br />
<br />
Follow these steps to determine the cause of your problem:<br />
<br />
* Check your PSU and microUSB cable ratings<br />
* Download and image a base image of Linux<br />
* Plug in power and Ethernet into your PINE64 device<br />
* Watch Ethernet port LED activity<br />
* Check your router for your device's IP<br />
* Attempt to ssh into your device's from your computer<br />
<br />
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 device then either the imaging process failed (possibly due to a subpar microSD) OR the PSU / microUSB cable is/are faulty.<br />
<br />
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.<br />
<br />
If neither of the above mentioned scenarios fits the problem you are facing, please consult this thread (thanks to Ghost for compiling the list): https://forum.pine64.org/showthread.php?tid=680<br />
<br />
If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/<br />
<br />
[[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10780Upgrade PineTime to InfiniTime 1.0.02021-06-19T06:51:42Z<p>JerseyDevil: category, formatting</p>
<hr />
<div>{{Note|Page under construction, information subject to review and feedback.}}<br />
<br />
Congratulations on receiving your new PineTime!<br />
<br />
From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those of us that are developing stuff for it, it's pretty easy and straightforward, but like with all technology, it is a bit tricky. <br />
<br />
{{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. With the display off, and battery fully charged, you can expect a wait of 5-7 days so it is best to not fully charge it. If it freezes with the display on, it will likely be flat by the end of the day. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br />
<br />
In a nutshell, you need to:<br />
# Charge your watch, but '''not''' to 100% - keep it at approximately 50% - for the reason described above.<br />
# Update InfiniTime<br />
# Update the bootloader<br />
# Install the recovery firmware<br />
<br />
= Update Process =<br />
So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has Bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo] or [https://github.com/piggz/harbour-amazfish Amazfish]. You can also use these applications on your Pinebook Pro or Pinephone if you happen to have those devices. <br />
<br />
The reason for installing the updates in the specified order is because newer versions of InfiniTime have a more robust Bluetooth update process, and since we're updating everything over Bluetooth, the fewer retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br />
<br />
[https://video.codingfield.com/videos/watch/831077c5-16f3-47b4-9b2b-c4bbfecc6529 This video] shows the bootloader and recovery firmware installation procedure.<br />
<br />
[https://video.codingfield.com/videos/watch/f7bffb3d-a6a1-43c4-8f01-f4aeff4adf9e This video] shows the bootloader installation and firmware update using Amazfish.<br />
<br />
You can also read a [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/339224cf5ed21f4e8b2d22eaeab9869120f7f752/docs/howToUpdate.md detailed installation procedure in the documentation of the bootloader].<br />
<br />
== Update InfiniTime ==<br />
To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br />
<br />
After updating InfiniTime, ensure that you validate the firmware to prevent it from being automatically reverted/rolled back if your watch is reset/restarted. To do this, swipe right to access the quick actions panel, press the gear/settings icon, swipe up once to show the second page, press on the 'Firmware' option and then on 'Validate'.<br />
<br />
[https://youtu.be/-5lwBd60k0Q Video showing validation process]<br />
<br />
<br />
=== Gadgetbridge ===<br />
<br />
# Connect your PineTime to GB<br />
# Download the aforementioned file to your phone<br />
# Find the file in your file manager<br />
# 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br />
# Confirm that you wish to apply the update<br />
# Wait for the update to complete<br />
<br />
[https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br />
<br />
=== NRFConnect ===<br />
<br />
# Download the aforementioned file to your phone.<br />
# Open NRFConnect<br />
# Scan for your device<br />
# Connect to it<br />
# Choose the DFU option at the top right of the screen<br />
# Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br />
# Select your previously downloaded file<br />
# Wait for the update to complete<br />
<br />
[https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br />
<br />
=== Siglo ===<br />
# If your device was not detected upon start, press "Rescan" to find it.<br />
# Select the "1.0.0" tag<br />
# Select the aforementioned file/asset.<br />
# Select "Flash It!"<br />
<br />
=== Amazfish ===<br />
# Run Amazfish (service + UI)<br />
# Pair with you device:<br />
## Unzip the DFU file to extract the .bin file.<br />
## Click on "pair with watch" on the top<br />
## Select "PineTime" (if your device is running InfiniTime 0.7.1 or lower) or "InfiniTime (if it's running InfiniTime 0.8+) and choose your device in the list<br />
# Click on "Download file" on the top <br />
# Click on "Choose file" and select the .bin file you extracted from the DFU file<br />
# Click on "Send file"<br />
# Wait for the update to complete.<br />
<br />
[https://video.codingfield.com/videos/watch/41cfcf5d-b0e6-4323-8056-b0a6682d1f25 See it in action!]<br />
<br />
== Update the bootloader ==<br />
To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/reloader-mcuboot.zip reloader-mcuboot.zip]. <br />
Once the bootloader is updated, you should notice that the boot logo has changed. Previously, it was a green "PineTime" logo, and now it is a large pinecone that is progressively drawn in green.<br />
<br />
[https://youtu.be/fvHQ8ZeqnOo Video showing what the InfiniTime 1.0.0 bootloader looks like]<br />
<br />
=== Using Gadgetbridge ===<br />
<br />
Same process as before, but with the file for this step.<br />
<br />
=== Using NRFConnect ===<br />
<br />
Same process as before, but with the file for this step.<br />
<br />
=== Using Siglo ===<br />
Same process as before, but select the "0.14.1" tag, and the file/asset for this step.<br />
<br />
=== Using Amazfish ===<br />
<br />
You may need to re-pair with your device by selecting "InfiniTime" (since you've already upgraded to InfiniTime 1.0) in the device type list. Then follow the same process as before, but with the file for this step.<br />
<br />
== Install the recovery firmware ==<br />
{{warning|1=Don't do this before updating the bootloader, otherwise your PineTime will freeze at the end of the process, and you will need to wait for the battery to go flat }} <br />
<br />
To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip]. You will know when this is running when it shows an InfiniTime logo with a progress bar running across the bottom whilst it is installing the recovery firmware. <br />
<br />
=== Using Gadgetbridge ===<br />
<br />
Same process as before, but with the file for this step.<br />
<br />
=== Using NRFConnect ===<br />
<br />
Same process as before, but with the file for this step.<br />
<br />
=== Using Siglo ===<br />
Same process as before, but with the file/asset for this step.<br />
<br />
=== Using Amazfish ===<br />
<br />
Same process as before, but with the file for this step.<br />
<br />
<br />
= Guides and Videos =<br />
<br />
= Troubleshooting =<br />
Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br />
<br />
Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature-complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charging cradle, it will power up and you should be right to try again.<br />
<br />
If you get stuck or have any questions, join us on your preferred [[Main_Page#Chat_Platforms|chat platform]] or the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.<br />
<br />
<br />
[[Category:PineTime]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=U-Boot&diff=10778U-Boot2021-06-19T06:31:42Z<p>JerseyDevil: category, formatting</p>
<hr />
<div>{{hint|It is helpful to have a debugging serial cable for this.}}<br />
<br />
= Building uboot manually =<br />
<br />
==Prerequisites==<br />
<br />
These instructions are written with a host Arch Linux desktop system in mind.<br />
<br />
This guide will be especially useful if you are looking to overclock the ram on your Pinephone following the information found [[Overclocking#DRAM|here]].<br />
<br />
You must have these packages installed: <code>dtc swig bc aarch64-linux-gnu-gcc</code><br />
<br />
If you are using a different system such as Ubuntu, there are plenty of cross compilation instructions available online with which you can grab the needed package names from, however you should be able to follow these instructions with these packages installed: <code>build-essentials bison flex swig gcc-aarch64-linux-gnu</code><br />
<br />
==Compilation==<br />
<br />
{{hint| This guide is written with the Pinephone in mind. On other devices you will need to set a different platform variable and likely use a different uboot source with patches oriented towards your device.}}<br />
<br />
Note by default these instructions utilize all of your computers cores to compile thanks to the <code>-j</code> and <code>$(nproc)</code> parameters. If you wish to only use one core to compile, or change the number of cores used for example to only two cores, then you can either completely remove the <code>-j$(nproc)</code> parameter from the make commands, or just take off <code>$(nproc)</code> and add the number of threads you want used in it's place: <code>-j4</code><br />
<br />
First, You need to compile ATF (Arm Trusted Firmware):<br />
<pre><br />
git clone https://github.com/crust-firmware/arm-trusted-firmware/<br />
cd arm-trusted-firmware<br />
export CROSS_COMPILE=aarch64-linux-gnu-<br />
export ARCH=arm64<br />
make PLAT=sun50i_a64 -j$(nproc) bl31<br />
cd ..<br />
</pre><br />
<br />
After ATF is compiled clone u-boot and copy the bl31.bin file into the u-boot directory.<br />
<pre><br />
git clone https://gitlab.com/pine64-org/u-boot.git<br />
cd arm-trusted-firmware<br />
cp build/sun50i_a64/release/bl31.bin ../u-boot/<br />
cd ..<br />
</pre><br />
<br />
<br />
{{hint| You cannot build [[crust]] if you do not have the or1k musl toolchain installed. This toolchain is not usually availible in distribution repositories and will have to be manually installed to the system. The following text will show a simple way to install the toolchain.}}<br />
<br />
Download the toolchain's archive: https://musl.cc/or1k-linux-musl-cross.tgz<br />
<br />
Extract the compressed archive: <code>tar zxvf or1k-linux-musl-cross.tgz</code><br />
<br />
Move the extracted archive to wherever you would like to install the toolchain to. In these instructions it will simply be installed to the users documents folder.<br />
<br />
The final step is to edit your <code>.bashrc</code> and add the following to the end:<br />
<br />
<pre><br />
# Path for or1k toolchain<br />
export PATH="$PATH:/home/USER/Documents/or1k-linux-musl-cross/bin/"<br />
#<br />
</pre><br />
<br />
After you've completed that you can close out the terminal and reopen it and proceed to the following instructions.<br />
<br />
<br />
<pre><br />
git clone https://github.com/crust-firmware/crust<br />
cd crust<br />
export CROSS_COMPILE=or1k-linux-musl-<br />
make pinephone_defconfig<br />
make -j$(nproc) scp<br />
cp /build/scp/scp.bin ../u-boot/<br />
cd ..<br />
</pre><br />
<br />
{{hint| If you do not wish to have [[crust]] in your uboot build, then you can skip exporting SCP}}<br />
<br />
<pre><br />
cd u-boot/<br />
git checkout crust<br />
export CROSS_COMPILE=aarch64-linux-gnu-<br />
export BL31=bl31.bin<br />
export ARCH=arm64<br />
export SCP=scp.bin<br />
make distclean<br />
make pinephone_defconfig<br />
make all -j$(nproc)<br />
</pre><br />
<br />
== Uboot installation ==<br />
<br />
Once successfully compiled you can proceed to flash the device<br />
{{warning|1= Replace [CHANGE THIS] with the location of your SD card and make sure you are using the proper location. Failure to do so can result in data loss.}}<br />
<code><br />
sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/[CHANGE THIS] bs=1024 seek=8<br />
</code><br />
{{hint|If you are compiling uboot in order to overclock your DRAM you can check if it was successful by reading the values of /sys/kernel/debug/clk/clk_summary}}<br />
<br />
=Pboot multi-bootloader=<br />
<br />
One of the smallest and fastest pinephone bootloaders, it was developed by Ondrej Jirman with the ability of booting multiple distros on the pinephone in mind.<br />
<br />
More information can be found [https://xnux.eu/p-boot/ here]<br />
<br />
= External Links =<br />
[https://linux-sunxi.org/Mainline_U-Boot Sunxi Uboot Wiki]<br />
<br />
[https://raw.githubusercontent.com/u-boot/u-boot/master/board/sunxi/README.sunxi64 Uboot build instructions]<br />
<br />
[https://musl.cc/or1k-linux-musl-cross.tgz or1k toolchain download]<br />
<br />
[[Category:PinePhone]][[Category:Guide]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Category:Guide&diff=10768Category:Guide2021-06-19T05:14:30Z<p>JerseyDevil: Created blank page</p>
<hr />
<div></div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:ROCKPro64v21REAR.jpg&diff=10766File:ROCKPro64v21REAR.jpg2021-06-19T01:31:21Z<p>JerseyDevil: category</p>
<hr />
<div>Hi-res picture of v2.1 rear<br />
<br />
[[Category:ROCKPro64]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:ROCKPro64v21FRONT.jpg&diff=10765File:ROCKPro64v21FRONT.jpg2021-06-19T01:31:08Z<p>JerseyDevil: category</p>
<hr />
<div>Hi-res top view of v2.1<br />
<br />
[[Category:ROCKPro64]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:ROCKPro64_annotated.jpg&diff=10764File:ROCKPro64 annotated.jpg2021-06-19T01:30:50Z<p>JerseyDevil: category</p>
<hr />
<div>This is the 3rd version of the annotated RockPro64 photo. I added it here as the updates of the old version don't appear but the old version is still shown instead.<br />
<br />
[[Category:ROCKPro64]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:NASCaseMain.png&diff=10763File:NASCaseMain.png2021-06-19T01:30:19Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:ROCKPro64]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinPower-Desktop-front-plate-removal.jpg&diff=10762File:PinPower-Desktop-front-plate-removal.jpg2021-06-19T01:19:51Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinPower-Desktop-Display-front.jpg&diff=10761File:PinPower-Desktop-Display-front.jpg2021-06-19T01:19:38Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinPower-Desktop-Display-back.jpg&diff=10760File:PinPower-Desktop-Display-back.jpg2021-06-19T01:19:17Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinPower-Desktop-PCB-top.jpg&diff=10759File:PinPower-Desktop-PCB-top.jpg2021-06-19T01:19:04Z<p>JerseyDevil: Category:PinePower</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinPower-Desktop-PCB-bottom.jpg&diff=10758File:PinPower-Desktop-PCB-bottom.jpg2021-06-19T01:18:50Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinPower-Desktop-wireless-charger.jpg&diff=10757File:PinPower-Desktop-wireless-charger.jpg2021-06-19T01:18:38Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinePower-Desktop-2.jpg&diff=10756File:PinePower-Desktop-2.jpg2021-06-19T01:18:26Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinePower_Charger_65W.jpeg&diff=10755File:PinePower Charger 65W.jpeg2021-06-19T01:18:07Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Category:PinePower&diff=10754Category:PinePower2021-06-19T01:17:42Z<p>JerseyDevil: Created blank page</p>
<hr />
<div></div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PinePower&diff=10753PinePower2021-06-19T01:17:06Z<p>JerseyDevil: category</p>
<hr />
<div>{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}<br />
<br />
== PinePower 65W GaN Charger ==<br />
[[File:PinePower_Charger_65W.jpeg|400px|thumb|right|PinePower 65W render]]<br />
A small and compact palm size 65W wall socket power adapter. It features 2 USB-C ports and 1 USB-A port charger. [https://en.wikipedia.org/wiki/Gallium_nitride Gallium Nitride] technology ensures a small and light charger with high charging efficiency. It has a retractable US plug.<br />
===General specifications===<br />
Body<br />
*Dimensions: 74.8mm x 36.6mm x 32mm<br />
*Weight: 130 grams<br />
*Build: Plastic<br />
*Color: Black<br />
<br />
Power<br />
*Input: AC 100-240V 50/60Hz 1.5A Max<br />
*Output: 65W<br />
*Power switch<br />
<br />
Connections<br />
* 240Vac input US plug, adapters for AU, EU, and UK,<br />
* 1x USB-A<br />
* 2x USB-C<br />
<br />
=== Power specifications ===<br />
{| class="wikitable"<br />
! Output<br />
! Max output power<br />
! Power ranges PD<br />
! Power ranges QC<br />
! Power ranges PPS<br />
<br />
|-<br />
| Single USB-C1 or C2<br />
| 65W<br />
| 5V3A, 9V3A, 12V3A, 15V3A, 20V3.5A<br />
| -<br />
| 3.3-11V5A<br />
|-<br />
| Single USB-A<br />
| 65W<br />
| -<br />
| QC3.0 4.5V5A, 5V4.5A, 9V3A, 12V3A, 20V3A<br />
| -<br />
|-<br />
<br />
|USB-C1 & <br />
USB-C2 combined<br />
| <br />
*45W<br />
*18W<br />
| <br />
*5V3A, 9V3A, 12V3A, 15V3A<br />
*5V3A, 9V2A, 12V1.5A<br />
| -<br />
| -<br />
|-<br />
<br />
| USB-C1 &<br />
USB-A combined<br />
| <br />
*45W<br />
*18W<br />
|<br />
*5V3A, 9V3A, 12V3A, 15V3A<br />
*-<br />
|<br />
*-<br />
*5V3A, 9V2A, 12V1.5A<br />
| -<br />
|-<br />
<br />
|USB-C1 &<br />
USB-C2 + USB-A combined<br />
|<br />
*45W<br />
*15W<br />
|<br />
*5V3A, 9V3A, 12V3A, 15V3A<br />
*5V3A<br />
| -<br />
| -<br />
|}<br />
<br />
===Internals===<br />
''TBA''<br />
<br />
== PinePower 120W Desktop Power Supply ==<br />
[[File:PinePower-Desktop-2.jpg|400px|thumb|right|PinePower Desktop 120W render]]<br />
A 120W desktop power adapter. It features 1 USB-C port and 4 USB-A port. The 120W output is not per port, but total output power. This is calculated by combining the 65W USB-C, 3x15W USB-A and the 18W USB-A QC, making a total of 128W. The only difference between the US and EU edition is the supplied power cable. Every port, with exception of the wireless Q-charger, has a display, portraying the output voltage and amps. The display back light can be turned on and off by capacitive touch button, located on the top left side of the unit.<br />
===General specifications===<br />
Body<br />
*Dimensions: 123mm x 115mm x 48mm<br />
*Weight: 543 grams<br />
*Build: Plastic<br />
*Color: Black<br />
<br />
Display<br />
*Individual port voltage status display<br />
*Individual port current status display<br />
*Display turn off switch<br />
<br />
Power<br />
*Input: AC 100-240V 50/60Hz ?A Max<br />
*Output: 120W<br />
*Power switch<br />
<br />
Connections<br />
* 240Vac input either US or EU plug is supplied<br />
* 4x USB-A<br />
* 1x USB-C<br />
<br />
=== Power specifications ===<br />
{| class="wikitable"<br />
! Output<br />
! Protocol<br />
! Version<br />
! Max output power<br />
! Power ranges<br />
|-<br />
<br />
| USB-C<br />
| [https://en.wikipedia.org/wiki/USB_hardware#USB_Power_Delivery_(USB_PD) PD]<br />
| ?<br />
| 65W<br />
| 5V3A, 9V3A, 12V3A, 15V3A, 20V3.25A<br />
|-<br />
<br />
| USB-A<br />
| [https://en.wikipedia.org/wiki/Quick_Charge QC]<br />
| 3.1<br />
| 18W<br />
| 5V3A, 9V2A, 12V1.5A<br />
|-<br />
<br />
| USB-A<br />
| USB<br />
| ?<br />
| 15W<br />
| 5V3A<br />
|-<br />
<br />
| Wireless charger<br />
| [https://en.wikipedia.org/wiki/Qi_(standard) Qi]<br />
| 1.2<br />
| 10W<br />
| -<br />
|}<br />
<br />
===Internals===<br />
<br />
The power unit is not made to be disassembled, do so at your own risk. The front plate is secured with 4 tabs, that can be disengaged with a screwdriver. The complete assembly can be slid out, but do mind the same tab in the casing. The power button at the back of the case has a plug that can be disconnected from the main PCB. The wireless charging PCB has to be de-soldered, or forcefully removed from the inner casing, as it is glued to the top of the case.<br />
<br />
<gallery mode="packed-hover" heights="180"><br />
File:PinPower-Desktop-front-plate-removal.jpg | (Removal of the front plate)<br />
File:PinPower-Desktop-Display-front.jpg | (Front view display PCB)<br />
File:PinPower-Desktop-Display-back.jpg | (Back side display PCB)<br />
File:PinPower-Desktop-PCB-top.jpg | (Top side main PCB)<br />
File:PinPower-Desktop-PCB-bottom.jpg | (Bottom view main PCB)<br />
File:PinPower-Desktop-wireless-charger.jpg | (Wireless charger)<br />
</gallery><br />
<br />
Some remarks:<br />
*This main PCB is marked as XR SEMI v1.1<br />
*Two unmarked packages, control the display. <br />
*An antenna is connected on the display PCB, lining up with the 'lamp' symbol. This is the capacitive touch button to control the display back light.<br />
*The 65W PD USB-C port is controlled by a [http://www.hynetek.com/product/pdController/HUSB339/document/HUSB339_DS_EN_V1.2.pdf HUSB339] controller, paired with a GOFORD G16 MOSFET.<br />
*The other ports have a [http://www.lshchip.com/pdf/Deep-pool/NDP1360KC_EN_Rev1.1.pdf NDP1360KC] as final power converter.<br />
<br />
==External links==<br />
*[https://www.pine64.org/2020/12/15/december-update-the-longest-one-yet/ Pine blog, containing news about the PinePower products]<br />
*[https://pine64.com/product/pinepower-65w-gan-2c1a-charger-with-international-plugs/ PinePower 65W on the official Pine store]<br />
*[https://pine64.com/product/pinepower-120w-desktop-power-supply-eu-version/ 120W EU version on the official Pine store]<br />
*[https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower 120W EU version on the official Pine store]<br />
<br />
[[Category:PinePower]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinecilTipSets.jpg&diff=10752File:PinecilTipSets.jpg2021-06-19T01:08:16Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil_Exploded_Diagram_ver_0.9.png&diff=10751File:Pinecil Exploded Diagram ver 0.9.png2021-06-19T01:07:41Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:PinecilPrototype.jpg&diff=10750File:PinecilPrototype.jpg2021-06-19T01:07:20Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil-bb2-01.jpg&diff=10749File:Pinecil-bb2-01.jpg2021-06-19T01:06:45Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil-Case-Red-1.jpg&diff=10748File:Pinecil-Case-Red-1.jpg2021-06-19T01:06:27Z<p>JerseyDevil: category</p>
<hr />
<div>== Summary ==<br />
Red Pinecil Casing from Pine64 store<br />
== Licensing ==<br />
{{subst:Unknown_copyright}}<br />
<br />
[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil-bb2-01_rotate.jpg&diff=10747File:Pinecil-bb2-01 rotate.jpg2021-06-19T01:05:56Z<p>JerseyDevil: category</p>
<hr />
<div>== Summary ==<br />
Pinecil in package, rotated<br />
<br />
[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil_breakout_bottom.jpg&diff=10746File:Pinecil breakout bottom.jpg2021-06-19T01:05:30Z<p>JerseyDevil: category</p>
<hr />
<div>== Summary ==<br />
Bottom view of Pinecil breakout board<br />
<br />
[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil_breakout_top.jpg&diff=10745File:Pinecil breakout top.jpg2021-06-19T01:04:39Z<p>JerseyDevil: category</p>
<hr />
<div>== Summary ==<br />
Top view of Pinecil breakout board<br />
<br />
[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Pinecil-breakout-board-02.jpg&diff=10744File:Pinecil-breakout-board-02.jpg2021-06-19T01:04:05Z<p>JerseyDevil: category</p>
<hr />
<div>[[Category:Pinecil]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:RK3566_icon.png&diff=10734File:RK3566 icon.png2021-06-17T21:42:45Z<p>JerseyDevil: categories</p>
<hr />
<div>[[Category:Quartz64]][[Category:Rockchip RK3566]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Rk35-blobs.tar.gz&diff=10733File:Rk35-blobs.tar.gz2021-06-17T21:41:26Z<p>JerseyDevil: categories, linkfix</p>
<hr />
<div>== Summary ==<br />
The directory rk/rkbin/bin/rk35 extracted from the [[Quartz64#Android SDK]] hosted at https://files.pine64.org/SDK/Quartz64/QUARTZ64_SDK_android11.tar.gz, uploaded, so that devs that only want a booting system without all the Android stuff can avoid downloading the 80GB SDK blob.<br />
<br />
[[Category:Quartz64]][[Category:Rockchip RK3566]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Category:Rockchip_RK3566&diff=10732Category:Rockchip RK35662021-06-17T21:38:34Z<p>JerseyDevil: Created blank page</p>
<hr />
<div></div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Quartz64_Development&diff=10731Quartz64 Development2021-06-17T21:37:46Z<p>JerseyDevil: categories</p>
<hr />
<div>This page documents the current status of software support for the [[Quartz64]] single-board computer, and provides links to resources to help prospective contributors get started. Information is kept current on a best-effort basis as various patches get accepted into the kernel.<br />
<br />
== Overview ==<br />
<br />
=== Upstreaming Status ===<br />
<br />
{| class="wikitable plainrowheaders" border="1"<br />
! scope="col" | Function<br />
! scope="col" colspan="2" | Status<br />
! scope="col" | Component<br />
! scope="col" | Notes<br />
|-<br />
! scope="row" | Video Output<br />
| colspan="2" style="background:#F99; text-align:center;"|Needs porting<br />
| <code>rockchipdrm/VOP-v2</code><br />
| <br />
|-<br />
! scope="row" | 3D Acceleration <br />
| style="background:PaleGreen; text-align:center;"|Linux Mainline<br />
| style="background:PaleGreen; text-align:center;"|Upstream Mesa<br />
| <code>panfrost</code><br />
| <br />
|-<br />
! scope="row" | Video Decode <br />
| style="background:LightYellow; text-align:center;"|Linux Staging<br />
| style="background:#F99; text-align:center;"|Not in ffmpeg<sup>[https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=2898]</sup><br />
| <code>hantro-vpu</code>, using <code>v4l2-requests</code><br />
| Speculative status on this also being hantro, can't find rk35* in drivers/staging/media/<br />
|-<br />
! scope="row" rowspan="2" | Audio <br />
| colspan="2" style="background:#F99; text-align:center;"|Needs porting<br />
| <code>snd-soc-rockchip-i2s?</code><br />
|<br />
|-<br />
| colspan="2" style="background:LightYellow; text-align:center;"|linux-next<sup>[https://lore.kernel.org/linux-devicetree/20210601140145.GH543307@dell/]</sup><br />
| <code>rk817-codec</code><br />
|<br />
|-<br />
! scope="row" | u-boot<br />
| colspan="2" style="background:LightYellow; text-align:center;"|Waiting on ATF sources<br />
|<br />
|<br />
|-<br />
! scope="row" | Device Tree<br />
| colspan="2" style="background:LightYellow; text-align:center;"|Early rk3568 dts in review<br />
| <br />
|<br />
|-<br />
! scope="row" rowspan="2"| Gigabit Ethernet<br />
| colspan="2" style="background:LightYellow; text-align:center;"|In review<sup>[https://patchwork.kernel.org/project/linux-rockchip/patch/20210421203409.40717-4-ezequiel@collabora.com/]</sup><br />
| <code>rk3566-gmac</code><br />
|<br />
|-<br />
| colspan="2" style="background:LightYellow; text-align:center;"|linux-next<sup>[https://git.kernel.org/netdev/net-next/c/48e8c6f1612b]</sup><br />
| <code>yt8511-phy</code><br />
|<br />
|-<br />
! scope="row" | IOMMU<br />
| colspan="2" style="background:LightYellow; text-align:center;"|In review<sup>[https://patchwork.kernel.org/project/linux-rockchip/list/?series=488139]</sup><br />
| <code>rockchip-iommu</code><br />
|<br />
|-<br />
! scope="row" | GPIO<br />
| colspan="2" style="background:LightYellow; text-align:center;"|In review<sup>[https://patchwork.kernel.org/project/linux-rockchip/list/?series=489333]</sup><br />
| <code>gpio-rockchip</code><br />
|<br />
|-<br />
! scope="row" | pinctrl<br />
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline<br />
|<br />
|<br />
|-<br />
! scope="row" | Thermal Regulation<br />
| colspan="2" style="background:LightYellow; text-align:center;"|In review<sup>[https://patchwork.kernel.org/project/linux-rockchip/patch/20210421200445.32977-1-ezequiel@collabora.com/]</sup><br />
| <code>rockchip-thermal</code><br />
|<br />
|-<br />
! scope="row" | PCIe<br />
| colspan="2" style="background:LightYellow; text-align:center;"|In review<sup>[https://patchwork.kernel.org/project/linux-rockchip/patch/20210506023448.169146-1-xxm@rock-chips.com/]</sup><br />
| <code>pcie-dw-rockchip</code><br />
|<br />
|-<br />
! scope="row" | Power Management<br />
| colspan="2" style="background:LightYellow; text-align:center;"|linux-next<sup>[https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=for-next&id=1782c87b44a0b1a527f01a6a184677c58ccbf9c7]</sup><br />
| <code>rockchip-pm-domain</code><br />
|<br />
|-<br />
! scope="row" | Voltage Control<br />
| colspan="2" style="background:LightYellow; text-align:center;"|In review<sup>[https://patchwork.kernel.org/project/linux-rockchip/patch/20210527082453.1447484-3-jay.xu@rock-chips.com/]</sup><br />
| <code>rk3568-pmu-io-voltage-domain</code><br />
|<br />
|-<br />
! scope="row" rowspan="2" | SPI <br />
| colspan="2" style="background:#F99; text-align:center;"|Needs a driver<br />
|<br />
|<br />
|}<br />
<br />
== Current Status ==<br />
<br />
The following sections give an overview over the current status of different parts of the board. Some parts are waiting on a driver to be written or ported, others only need various adjustments.<br />
<br />
General performance is poor, this is likely due to the [https://en.wikipedia.org/wiki/Advanced_Microcontroller_Bus_Architecture AHB bus] running slow, and may require some major rework of the clock layout to get to acceptable speeds.<br />
<br />
=== Working ===<br />
<br />
* eMMC<br />
* SDMMC0 (SD cards)<br />
* GMAC (Gigabit Ethernet)<br />
* USB 2.0<br />
* SATA 2<br />
* SATA 3<br />
* UART<br />
** UART 0 (Pi-bus)<br />
** UART 1 (Bluetooth)<br />
** UART 2 (Pi-bus, debug)<br />
* Video Decode<br />
** VP8<br />
<br />
=== Partially Working ===<br />
<br />
* PCI-Express Controller &mdash; everything but devices that need cache coherency (e.g. dGPUs) should work<br />
* USB 3.0 &mdash; at 2.0 speeds only, appears to be due to a PHY configuration issue<br />
* SDMMC1 (Wi-Fi) &mdash; AP6256 working, BL602 needs some work to make it flash firmware<br />
* I<sup>2</sup>C &mdash; works but is not yet exposed to the Pi-bus<br />
<br />
=== Confirmed Broken ===<br />
<br />
* Nothing!<br />
<br />
=== Needs Testing ===<br />
<br />
* GPU &mdash; Need a VOP-v2 DRM driver to get display output<br />
* Battery<br />
* Audio &mdash; Needs I2S driver<br />
* E-Paper<br />
* SPI &mdash; Needs a driver<br />
<br />
== Resources ==<br />
=== Repositories ===<br />
<br />
* BSP based development effort for SPL/U-Boot and Linux<br />
** https://gitlab.com/pine64-org/quartz-bsp<br />
* Image CI pipeline aimed at developers<br />
** https://gitlab.com/pgwipeout/quartz64_ci/<br />
* Rockchip U-Boot<br />
** https://github.com/rockchip-linux/u-boot<br />
<br />
=== Other ===<br />
<br />
* Rockchip-SoC Patchwork Page<br />
** https://patchwork.kernel.org/project/linux-rockchip/list/<br />
* Rockchip Kernel Mailing List Archive<br />
** https://lore.kernel.org/linux-rockchip/<br />
<br />
== Board/SoC Documentation ==<br />
=== Booting ===<br />
==== Boot Order ====<br />
The RK3566 boot ROM will search for a valid ID BLOCK in the following order on the support boot media:<br />
<br />
* SPI NOR flash<br />
* SPI NAND flash<br />
* eMMC<br />
* SD-Card<br />
<br />
... if this fails, the boot ROM will initialize the USB0 port and wait for a connection from the Rockchip<br />
flash/boot tools.<br />
<br />
==== Bootloader Flashing ====<br />
<br />
As per pgwipeout's [https://gitlab.com/pine64-org/quartz-bsp/u-boot/-/commit/12d102b86813378af08b086f3b9c13ed8010754c commit message]:<br />
* Make a partition named <code>uboot</code> as partition number 1 at 8 MiB to 16 MiB<br />
* <code>dd if=idblock.bin of=/dev/''<mmc/sd>'' seek=64</code><br />
* <code>dd if=uboot.img of=/dev/''<mmc/sd>''1</code><br />
<br />
==== BSP Image Layout ====<br />
<br />
[[Category:Quartz64]][[Category:Rockchip RK3566]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Category:Quartz64&diff=10730Category:Quartz642021-06-17T21:27:21Z<p>JerseyDevil: Created blank page</p>
<hr />
<div></div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=10714PinePhone Software Releases2021-06-13T19:40:58Z<p>JerseyDevil: borrow logos nix and nemo from another page</p>
<hr />
<div>This page contains a list of all available releases for the [[PinePhone]] as well as links to other resources.<br />
<br />
See [[PinePhone Installation Instructions]] on how to install the operating systems. However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]]<br />
<br />
{{Hint| Note: Some releases may not have a good setup for the backlight at low brightness. If configured too low the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}<br />
<br />
= Software Releases =<br />
<br />
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used, if possible required patches are included.<br />
<br />
== Arch Linux ARM ==<br />
<div style=float:right>[[File:Archlinux-logo.png|100px]]</div><br />
<br />
(Unofficial) Arch Linux ARM with choice of Phosh UI or barebones, currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub [https://github.com/DanctNIX/danctnix 1] [https://github.com/dreemurrs-embedded 2]).<br />
<br />
'''Download location'''<br />
<br />
Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
'''username/password'''<br />
<br />
alarm/123456<br />
<br />
'''What works, what does not work'''<br />
<br />
Most of the things now works, there are some minor issues with [[crust]].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].<br />
<br />
== ExpidusOS ==<br />
<br />
A fork of Void Linux with a custom fork of XFCE as the default desktop environment, developed by [https://midstall.com/ Midstall Software].<br />
<br />
* [https://expidusos.com ExpidusOS official website]<br />
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]<br />
* [https://discord.gg/GVfBF2w Midstall Software Discord server]<br />
<br />
'''Download location'''<br />
<br />
Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".<br />
<br />
'''username/password'''<br />
<br />
expidus/expidus<br />
<br />
'''What works, what does not work'''<br />
<br />
The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
GitHub: https://github.com/ExpidusOS<br />
<br />
== Fedora ==<br />
<div style=float:right>[[File:Fedora-logo.png|100px]]</div><br />
<br />
An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum].<br />
<br />
'''Download location'''<br />
<br />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/ build scripts]<br />
<br />
There is also an FTP server with full a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)<br />
<br />
'''username/password'''<br />
<br />
pine/123456<br />
<br />
'''What works, what does not work'''<br />
<br />
WiFi, Bluetooth, SMS, Data, Calls all work!<br />
<br />
There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution. <br />
<br />
'''How to contribute and report defects'''<br />
<br />
Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker]. Be sure to include logs if applicable! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github].<br />
<br />
== Gentoo ==<br />
<div style=float:right>[[File:GentooLogo.png|100px]]</div><br />
<br />
There are unofficial Gentoo overlays with ebuilds for the PinePhone. There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.<br />
You will be using the [https://wiki.gentoo.org/wiki/Project:ARM64 arm64] version of Gentoo. <br />
<br />
'''Documentation'''<br />
<br />
https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone<br />
<br />
https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone<br />
<br />
https://wiki.gentoo.org/wiki/PinePhone (incomplete)<br />
<br />
'''Overlay locations'''<br />
<br />
https://gitlab.com/bingch/gentoo-overlay/<br />
<br />
https://github.com/stealthgun/gjdwebserver-overlay/<br />
<br />
== GloDroid ==<br />
<br />
{{warning|Available images are outdated and do not reflect the state of the current developments.}}<br />
<br />
A fully open source port of Android to the PinePhone<br />
<br />
'''Download location'''<br />
<br />
https://github.com/GloDroid/glodroid_manifest/releases<br />
<br />
'''What works, what does not work'''<br />
<br />
Works: WiFi, screen dimming, touchscreen and charging work.<br />
Don't work: Bluetooth, Telephony, GPS<br />
<br />
== LuneOS ==<br />
<br />
LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by [https://www.webos-ports.org/wiki/Main_Page WebOS Ports] community.<br />
<br />
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Pinephone Wiki page]<br />
<br />
'''Download location'''<br />
<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
<br />
Tofe recommends using bmaptool, which is way faster than dd, and can decompress images on-the-fly.<br />
<br />
Syntax is:<br />
<br />
<code>bmaptool copy [from] [to]</code><br />
<br />
For example:<br />
<br />
<code>bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0</code><br />
<br />
.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require .img files.<br />
<br />
== Maemo Leste ==<br />
<div style=float:right>[[File:Maemoleste-logo.png|100px]]</div><br />
<br />
[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. <br />
<br />
The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.<br />
<br />
More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions]. <br />
<br />
'''Download location'''<br />
<br />
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].<br />
<br />
'''username/password'''<br />
<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
'''What works, what does not work'''<br />
<br />
For current status and workarounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on the project's Github page, see below).<br />
<br />
'''How to contribute and report defects'''<br />
<br />
Most discussion occurs at <i>#maemo-leste</i> on <i>irc.libera.chat</i>. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.<br />
<br />
All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]. Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available.<br />
<br />
== Manjaro ARM ==<br />
<div style=float:right>[[File:Manjaro-logo.svg|100px]]</div><br />
<br />
Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.<br />
<br />
'''Download location'''<br />
<br />
*Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]<br />
*Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]<br />
*Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev]<br />
<br />
'''username/password'''<br />
<br />
manjaro/123456<br />
<br />
root/root<br />
<br />
'''What works, what does not work'''<br />
<br />
{{Hint| Note: The Phosh image the boot will load at a TTY login prompt for multiple minutes at the first boot.}}<br />
<br />
See Manjaro's release announcements on their forum.<br />
<br />
Recent ones: [https://forum.manjaro.org/t/manjaro-arm-beta8-with-phosh-pinephone/62260 Phosh], [https://forum.manjaro.org/t/manjaro-arm-beta4-with-plasma-mobile-pinephone/62363 Plasma] and [https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].<br />
<br />
== Mobian ==<br />
<div style=float:right>[[File:Debian-logo.png]]</div><br />
<br />
An unofficial Debian build for ARM64 running with the Phosh user interface (developed by Purism, Phosh uses Wayland instead of Xorg). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot). Current version is Debian Bullseye.<br />
<br />
'''Download location'''<br />
<br />
[https://images.mobian-project.org/pinephone/nightly/ Nightly] / [https://images.mobian-project.org/pinephone/installer/ Installer] / [https://images.mobian-project.org/pinephone/ Stable]<br />
<br />
Don't forget to extract the image before installing:<br />
<br />
<code>$ gzip -d Downloads/mobian-pinephone-*.img.gz</code><br />
<br />
See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.<br />
<br />
'''username/password'''<br />
<br />
mobian/1234<br />
<br />
'''What works, what does not work'''<br />
<br />
See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki]for most up to date status.<br />
<br />
Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker]. As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask. Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].<br />
<br />
'''Notes'''<br />
<br />
See [[Mobian for PinePhone]] or [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.<br />
<br />
== Multi-boot demo image ==<br />
<br />
{{Warning| This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}<br />
<br />
The purpose of this image is for users to easily try many of the above Linux distributions, without having to figure out how to flash them individually and juggle with many microSD cards.<br />
<br />
* More information can be found at: https://xnux.eu/p-boot-demo/<br />
* Git repo: https://megous.com/git/pinephone-multi-boot/<br />
* [https://forum.pine64.org/showthread.php?tid=11347 Discussion on the forum]<br />
<br />
== Nemo Mobile ==<br />
<div style=float:right>[[File:nemo_mobile.png|right|100px]]</div><br />
Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), now [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro]. See their website [https://nemomobile.net/ Nemo Mobile UX team] and [https://wiki.merproject.org/wiki/Nemo Mer Wiki page].<br />
<br />
You can either install Nemo on any device that already runs Sailfish, or flash a prebuilt image to SD card/emmc on the PinePhone to install.<br />
<br />
'''Download location'''<br />
<br />
{{Hint| Note: See their website for the newest release and installation guides.}}<br />
<br />
Prebuilt images:<br />
<br />
First devel image for Manjaro (April 1, 2021):<br />
<br />
* Offical blog post: [https://nemomobile.net/pages/Hello_manjaro/ First devel image for manjaro]<br />
* Image locations:<br />
** devel: https://img.nemomobile.net/devel/<br />
** ?: https://img.nemomobile.net/2021.05/<br />
* Packages: https://img.nemomobile.net/manjaro/05.2020/stable/<br />
<br />
Nemo with Glacier UX v0.8 (April 27, 2020):<br />
<br />
* Offical blog post: [https://nemomobile.net/pages/Nemo_For_pinephone/ Nemo for PinePhone v0.8]<br />
* rootfs image: https://yadi.sk/d/VAbtKV-Hnql60g<br />
* 2GB sdcard image: https://yadi.sk/d/8oSZp-frGidscw<br />
<br />
Install Nemo on Sailfish:<br />
<br />
Install Sailfish on your PP first (follow instructions on the [[PinePhone_Software_Releases#Sailfish_OS|Sailfish]] section on this page).<br />
<br />
Enable developer mode. In the terminal, run as root (`devel-su`):<br />
<br />
<code>ssu ar nemo-devel-ux http://repo.merproject.org/obs/home:/neochapay:/nemo-ux/sailfish_latest_armv7hl/ </code><br />
<br />
then:<br />
<br />
<code>pkcon refresh </code><br />
<br />
then install the nemo-specific Glacier packages:<br />
<br />
<code>pkcon install lipstick-glacier-home-qt5 </code><br />
<br />
If necessary, reboot.<br />
<br />
'''What works, what does not work'''<br />
<br />
For the newer devel image based on Manjaro, [https://twitter.com/neochapay/status/1374029467526500355 Wi-Fi and Bluetooth works].<br />
<br />
For the older Nemo with Glacier UX v0.8, voicecalls, sound and cameras do not work by default, see its blog post and GitHub repo readme.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
For the Nemo Mobile UX itself:<br />
* GitHub issues: https://github.com/nemomobile-ux/main/issues<br />
<br />
For hardware:<br />
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues<br />
<br />
== NixOS ==<br />
<div style=float:right>[[File:nixos.png|right|100px]]</div><br />
NixOS support is handled through the Mobile NixOS project.<br />
<br />
* [https://mobile.nixos.org/ Project home page]<br />
<br />
* [https://github.com/NixOS/mobile-nixos Source code repository]<br />
<br />
There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].<br />
<br />
'''What works, what does not work'''<br />
<br />
This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use WiFi.<br />
<br />
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues. Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].<br />
<br />
== OpenMandriva Lx ==<br />
{{Hint| Note: This image is solely for testing purposes.}}<br />
<br />
OpenMandriva Lx with Plasma Mobile as UI.<br />
<br />
'''Download location'''<br />
<br />
The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ here]. See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-2-rc-available-for-testing here] for the announcement.<br />
<br />
== openSUSE ==<br />
<div style=float:right>[[Image:SLEM-OS-logo.png|100px|link=https://www.opensuse.org/]]</div><br />
<br />
Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images, except what needs to be changed for the PinePhone. The images include <i>zypper</i> (RPM) as the default package manager and have access to virtually the same (open source) software as our desktop repositories, thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports. Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.<br />
<br />
'''Download links'''<br />
<br />
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]<br />
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]<br />
<br />
To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key]. Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.<br />
<br />
You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.<br />
<br />
'''Username/Password'''<br />
<br />
The login credentials are pine/1234 and root/linux. Change (or disable) the root password once you are set up.<br />
<br />
'''What works and what does not work'''<br />
<br />
You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].<br />
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].<br />
You will also find information in our wiki on how to report issues (Contributing section).<br />
<br />
== postmarketOS ==<br />
<div style=float:right>[[File:PostmarketOS-logo.png|100px]]</div><br />
<br />
postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.<br />
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).<br />
<br />
As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo. The official images come in two flavors, either as demo image to try out postmarketOS, or with the installer.<br />
<br />
When using the installer images (recommended), it is possible to:<br />
* encrypt your installation<br />
* install from the SD card to eMMC<br />
<br />
Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.<br />
<br />
Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.<br />
<br />
'''Download location'''<br />
<br />
* [https://postmarketos.org/download/ Download page]<br />
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]<br />
<br />
'''Username/password'''<br />
<br />
user/147147<br />
<br />
This is for demo images only - when using the installer images or building an image with pmbootstrap, you set your own username and password. The Phosh and Plasma Mobile lock screens require your password, but they only present a numeric keyboard, so you should use '''only''' numbers in your password.<br />
<br />
'''What works, what does not work'''<br />
<br />
See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support. See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.<br />
<br />
== PureOS ==<br />
<div style=float:right>[[File:Pureos.png|100px]]</div><br />
<br />
{{Warning|This project is no longer under development and has been abandoned.}}<br />
<br />
{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}<br />
<br />
[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian Buster and GNOME developed by the Purism community.<br />
<br />
* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there<br />
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]<br />
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS<br />
<br />
'''Download location'''<br />
<br />
Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.<br />
<br />
Also see:<br />
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]<br />
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi<br />
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone<br />
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com<br />
<br />
== Sailfish OS ==<br />
<div style=float:right>[[File:Sailfish_logo.png|150px]]</div><br />
<br />
[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].<br />
<br />
* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.<br />
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]<br />
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]<br />
<br />
'''Download location'''<br />
<br />
'''Flashing script'''<br />
<br />
The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].<br />
<br />
The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card. Note: The script will format and erase the SD card!<br />
<br />
Instructions:<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Verify that you have the <code>bsdtar</code> package installed<br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc. <br />
<br />
<br />
'''username/password'''<br />
<br />
Set PIN on initialization.<br />
<br />
* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.<br />
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''<br />
* When a screen with a loading circle is displayed, just left/right swipe it away.<br />
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.<br />
<br />
'''What works, what does not work'''<br />
<br />
See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.<br />
<br />
There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.<br />
<br />
Git repo links are at the top of this OS section. other repos that may be helpful:<br />
<br />
* [https://github.com/sailfish-on-dontbeevil GitHub project page]<br />
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]<br />
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)<br />
<br />
See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.<br />
<br />
'''Notes'''<br />
<br />
OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[crust]] or changes of partition layout are added, then you need to reflash.<br />
<br />
== SkiffOS ==<br />
<div style=float:right>[[File:SkiffOS-Icon-1.png|100px]]</div><br />
<br />
Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.<br />
<br />
Provides the reliability of firmware with the ease-of-use of package managers.<br />
<br />
Upgrade over-the-air via a simple rsync script, or copying 3 files.<br />
<br />
Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.<br />
<br />
Use configuration packages to configure distro:<br />
* core/pinephone_neon: KDE Neon via Ubuntu repositories<br />
* core/pinephone_nixos: Nixos Mobile<br />
* core/pinephone_gentoo: Gentoo with Link-time Optimization & KDE Mobile or Phosh<br />
* core/pinephone_ubports: Ubuntu Ports for PinePhone<br />
* core/pinephone_manjaro_kde: Manjaro for PinePhone: KDE variant<br />
* core/pinephone_manjaro_phosh: Manjaro for PinePhone: Phosh variant<br />
* core/pinephone_manjaro_lomiri: Manjaro for PinePhone: Lomiri variant<br />
<br />
<br />
The boot-up OS is upgraded independently from the containers.<br />
<br />
'''Download location'''<br />
<br />
The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].<br />
<br />
== Sxmo ==<br />
<br />
A collection of Suckless programs to create a mobile UI. Based on postmarketOS<br />
<br />
'''Download location'''<br />
<br />
Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the <i>/pine64-pinephone/sxmo/</i> sections respectively).<br />
<br />
'''username/password'''<br />
<br />
user/147147<br />
<br />
'''How to contribute and report defects'''<br />
<br />
All the contributing information is [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].<br />
<br />
== Ubuntu Touch ==<br />
<div style=float:right>[[File:Ubports-logo.png|100px]]</div><br />
<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
Ubuntu touch is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.<br />
<br />
'''Download location'''<br />
<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
'''username/password'''<br />
<br />
Set up during boot<br />
<br />
'''What works, what does not work'''<br />
<br />
Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].<br />
<br />
'''How to contribute and report defects'''<br />
<br />
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.<br />
<br />
= Tools =<br />
<br />
There are software tools, that can be booted on the PinePhone.<br />
<br />
== JumpDrive ==<br />
<br />
JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].<br />
<br />
See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image. Make sure to download the "PinePhone" image and to unpack the archive before flashing.<br />
<br />
= Factory Test OS =<br />
On the Braveheart model there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC. The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later. Since the 20200501 version, it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests. Do not flash eMMC to test your device, just dd it to microSD and test from there. New versions are distributed as part of the postmarketOS distribution.<br />
<br />
Links:<br />
[https://images.postmarketos.org/pinephone/ Software Images] (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)<br />
[https://gitlab.com/MartijnBraam/factorytest Git repo]<br />
[https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]<br />
<br />
== Factory-loaded OS builds ==<br />
<br />
These are different operating system builds that was preloaded in the factory with testing utility.<br />
<br />
Download the build, extract the image and dd it to the microSD and then insert it into the phone. Power up the PinePhone, perform and complete the test routine, then apply the build from microSD card to eMMC.<br />
<br />
dd the image on a 8 GB microSD card or larger.<br />
<br />
{| class="wikitable"<br />
! OS<br />
! Download<br />
! File Size<br />
! MD5<br />
|-<br />
| Beta Edition<br />
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz Direct download from pine64.org]<br />
| 1.78GB<br />
| f16bce93504a52217540ac886863a418<br />
|-<br />
| Mobian<br />
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz Direct download from pine64.org]<br />
| 1.41GB<br />
| 015be381ff4e650a7fca6d4eaa90d63d<br />
|-<br />
| KDE<br />
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz Direct download from pine64.org]<br />
| 2.28GB<br />
| 32979ff17b5ec4d358ce99f1aff0c77c<br />
|-<br />
| Manjaro<br />
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz Direct download from pine64.org]<br />
| 1.04GB<br />
| 4edfd4dceaefdd32a3417c1727161c29<br />
|-<br />
| postmarketOS<br />
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz Direct download from pine64.org]<br />
| 517MB<br />
| 244093be2f6d728fcbd1d29114607727<br />
|-<br />
| Ubuntu Touch<br />
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz Direct download from pine64.org]<br />
| 1.05GB<br />
| 2d7f5271e7a281db8f1b1219bedbe131<br />
|}<br />
<br />
= Installing other ARM64 distributions =<br />
<br />
{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.}}<br />
<br />
{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}<br />
<br />
If you would like to see specific commands for how to complete these steps, see:<br />
* https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or<br />
* https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
General step:<br />
<br />
# Create a boot (from 4 MB to about 252 MB) and root (from the end of boot to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.<br />
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files (in archive mode: like <code>rsync -ar</code>).<br />
# Edit <code>/etc/fstab</code> to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/<br />
# Follow the README instructions, which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.<br />
<br />
= Other Resources =<br />
Community<br />
* [[Main_Page#Community_and_Support|Links to the community services]]<br />
<br />
Hardware information<br />
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki<br />
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]<br />
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]<br />
<br />
Other software information<br />
* [https://linux-sunxi.org/Main_Page sunxi community wiki]<br />
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]<br />
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]<br />
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]<br />
<br />
Other<br />
* [https://pine64.com/?post_type=product Pine64 shop]<br />
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]<br />
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]<br />
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]<br />
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]<br />
<br />
<br />
[[Category:PinePhone]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil&diff=10713Project Don't be evil2021-06-13T19:35:35Z<p>JerseyDevil: uploaded and embedded logos -- Software entries should probably point to phone software page now?</p>
<hr />
<div>= The Project "Don't be evil" - Phase 2 of PINE64 Smartphone "PinePhone" Development Kit =<br />
<br />
Project Don't be evil is an actual smartphone developer kit for the PINE64 Smartphone dubbed "PinePhone". It is used in the early stages of development as a starting point for affiliated projects. <br />
PinePhone development has been broken down into three distinct phases: <br />
* First phase - Project Anakin <br />
* Second phase - purpose-built development kit code named "Don't be evil" and introduced at FOSDEM 2019 <br />
* Lastly, the third phase which is the PinePhone itself - scheduled to be prototype released in Q3 2019 and BTO batch released with mobile OS parents in Q4 2019 (pending on software development).<br />
<br />
[[Image:Qee3ovj.jpg|200px]]<br />
[[Image:Qsud2Gt.jpg|200px]]<br />
[[Image:Martijnpocket.jpg|200px]]<br />
<br />
= Project Don't be evil, Baseboard and SOPine Module Information, and Schematics =<br />
* Baseboard Dimensions: 165mm x 76mm x 19.5mm<br />
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, USB type-C connector<br />
* Baseboard Schematic:<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit%20Board%20Structure.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Structure]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.1.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.1 Schematic]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone%20Dev%20Kit%20Ver%201.1_PCB.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.1 PCB Artwork]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.2.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.2 Schematic]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone%20Dev%20Kit%20Ver%201.2_PCB.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.2 PCB Artwork]<br />
* SOPine Module Schematic:<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]<br />
* Wifi/BT module information:<br />
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]<br />
* [https://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)]<br />
<br />
<br />
= SoC and Memory Specification =<br />
* Based on Allwinner A64/R18<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
<div style=float:right>[[File:Allwinner_A64.jpg]] [[File:Allwinner_R18.png]]</div><br />
<br />
== CPU Architecture ==<br />
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]<br />
* A power-efficient ARM v8 architecture<br />
* 64 and 32bit execution states for scalable high performance<br />
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function<br />
* Support Large Physical Address Extensions(LPAE)<br />
* VFPv4 Floating Point Unit<br />
* 32KB L1 Instruction cache and 32KB L1 Data cache<br />
* 512KB L2 cache<br />
<br />
== GPU Architecture ==<br />
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]<br />
* Support OpenGL ES 2.0 and OpenVG 1.1 standard<br />
<br />
== System Memory ==<br />
* RAM Memory Variants: 2GB LPDDR3.<br />
* Storage Memory: SPI Flash and optional eMMC module from 16GB up to 64GB<br />
<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Allwinner A64/R18 SoC information:<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]<br />
* X-Powers AXP803 PMU (Power Management Unit) information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]<br />
* '''Project Don't be evil module/component related information:'''<br />
** 2MPixel front CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC20355Mp-module_for_pinephone_devkit.pdf 2MP CMOS Image Sensor Module Drawing]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC2035%20Product%20Brief.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Product Brief]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC2035%20DataSheet.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Datasheet]<br />
** 5MPixel Rear CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/ATK-OV5640-5Mp-module_for_pinephone_devkit.pdf 5MP CMOS Image Sensor Module Drawing]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OmniVision OV5640 5MP CMOS Image Sensor Datasheet]<br />
*** [https://www.arducam.com/downloads/modules/OV5640/OV5640_Software_app_note_parallel.pdf OmniVision OV5640 5MP CMOS Image Sensor Software Application Note]<br />
** LCD Touch Screen Panel information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" 1440x720 IPS LCD Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/JD9365D_DS_Preliminary_V0.01_20170427.pdf fiti JD9365D LCD Controller Datasheet]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" Front Panel Touch Screen Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/FT6336GU_Upgrade_Spec_Ver1.0.pdf FocalTech FT6336GU Front Panel Touch Screen Specification]<br />
** Lithium Battery information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/ncr18650b.pdf Panasonic NCR18650B 3350mAH Lithium Ion Battery Specification]<br />
** Ethernet PHY information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver]<br />
** Wifi/BT module information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** LTE module information:<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf Quectel EG25-G LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25&EC21_QuecCell_AT_Commands_Manual_V1.1.pdf Quectel EC25 LTE Module AT Cammands Set Manual]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Reference_Design_Rev.D_20161111.pdf Quectel EC25 LTE Module Reference Design Guide]<br />
** Sensors:<br />
*** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]<br />
*** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS Datasheet]<br />
*** [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]<br />
<br />
<br />
<br />
= Software and OS Image Downloads =<br />
<br />
== Postmarket OS Early Alpha test build [microSD Boot] ==<br />
<div style=float:right>[[File:postmarketos.png|right|100px]]</div><br />
* Suitable for PinePhone "Don't Be Evil" Dev Kit version 1.1 and version 1.2<br />
* There are two type of LCD panels. For long touch screen cable, please use the build with inverted wording.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://images.postmarketos.org/pinephone/ Direct download from postmarketOS image site]<br />
** [https://wiki.postmarketos.org/wiki/Pine_Don%27t_be_evil_devkit_(pine-dontbeevil) postmarketOS PinePhone "Don't Be Evil" dev kit wiki site]<br />
<br />
== UBPorts mainline build ==<br />
<div style=float:right>[[File:ubports.png|right|100px]]</div><br />
* [https://ci.ubports.com/job/rootfs-pinephone/ UBPorts Jenkins for PinePhone]<br />
<br />
The link above seems to be broken, if so try this:<br />
[https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ Jenkins Project rootfs-pinephone]<br />
<br />
== KDE Plasma Mobile build ==<br />
<div style=float:right>[[File:plasma_mobile.png|right|100px]]</div><br />
* Not Yet Ready *<br />
<br />
== Sailfish OS build ==<br />
<div style=float:right>[[File:sailfishos.png|right|100px]]</div><br />
The Sailfish OS image is build on Gitlab CI, the latest image can be installed using our [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script] written in Bash.<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card.<br />
<br />
'''Instructions:'''<br />
<br />
1. Download the flashing script<br />
<br />
2. Insert a microSD card in your device<br />
<br />
3. Make the script executable: <code>chmod +x flash-it.sh</code><br />
<br />
4. Execute it: <code>./flash-it.sh</code><br />
<br />
5. Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
'''Note''': The script will format and flash the SD card, make sure that you don't have any important data on the SD card!<br />
<br />
<br />
== Maemo Leste build ==<br />
<div style=float:right>[[File:maemo_leste.png|right|100px]]</div><br />
* Works on dev kit versions 1.1 and 1.2 <br />
* DD image to a micro SD (8GB+) or eMMC <br />
** [https://maedevu.maemo.org/images/pinephone-dontbeevil/ Maemo Leste test builds download]<br />
<br />
== NixOS build ==<br />
<div style=float:right>[[File:nixos.png|right|100px]]</div><br />
* Not Yet Ready *<br />
<br />
== LuneOS build ==<br />
<div style=float:right>[[File:luneos.jpg|right|100px]]</div><br />
* [https://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone and thanks to Tofe]<br />
* Tofe recommends using bmaptool ; for example "bmaptool copy https://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0" <br />
<br />
== Nemo Mobile build ==<br />
<div style=float:right>[[File:nemo_mobile.png|right|100px]]</div><br />
* Not Yet Ready *<br />
<br />
= Mali-400 64-bit Driver =<br />
<br />
== Mali-400 64-bit Driver [20171220] ==<br />
* [[Mali_Driver|Mali 64-bit X11 and Wayland Driver Download]]<br />
<br />
<br />
== Quick Links to Build Sources of OS Images ==<br />
* [https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix A64 mainline status matrix chart]<br />
<br />
'''Some these OS images labelled as <span style="color:#FF0000">beta or nightly builds</span> which means they are only fit for testing purposes<br />
<br />
'''These images should be <span style="color:#FF0000">used at your own risk</span> and are not fit for normal use'''<br />
<br />
* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]<br />
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]<br />
<br />
= Errata for ver1.1 and ver1.2 board =<br />
<br />
'''1. Please DON'T insert micro SIM card to dev kit board micro SIM card slot, the SIM data, VPP, and GND signal have been misplaced. A miciPCIe adapter with sim card holder 9shown as below photo) will be provide to developers to correct this mistake.'''<br />
<br />
[[File:MiniPCIe_with_sim_slot_adapter.png|200px]]<br />
<br />
<br />
'''2. The PinePhone dev kit doesn't charge due to VBUS on SOPine module is not connected. Please connect R9688 solder pads with 0 ohm resistor or using thin wire bridge up the solder pads. Location shows as below:'''<br />
<br />
[[File:PinePhone_VBUS_charging_small.png|200px]]<br />
<br />
<br />
'''3. The SOPINE's SPI NOR flash storage and the devkit's camera flash (heh) share the same GPIO pins. The flash storage may not be used.'''<br />
<br />
[[File:SOPINE-SPI-Flash.png|200px]] [[File:Pinephone-1.1-flash-schematic.png|200px]]<br />
<br />
<br />
'''4. On the camera flash GPIO conflict, the new assignment of GPIO PB3 pin for SGM3140 FLASH_EN and GPIP PD7 for FLASH_TRIGOUT. Please note that PD7 is also LCD_ID pin which may not be used.'''<br />
<br />
[[File:GPIO_PB3_location.jpg|200px]]<br />
GPIO PB3 location<br />
<br />
[[File:U54_SGM3140_FLASH_EN pin location.jpg|200px]]<br />
U54 SGM3140 FLASH_EN pin location<br />
<br />
[[File:Flash_GPIO_Reassigned.jpg|200px]]<br />
Flash GPIOs Reassigned wiring<br />
<br />
= Other Resources =<br />
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]<br />
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]<br />
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]<br />
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]<br />
* [https://osmocom.org/projects/quectel-modems/wiki/EC25/24 Quectel EC-25 LTE module open source information]<br />
<br />
[[Category:PinePhone]] [[Category:Allwinner A64]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Plasma_mobile.png&diff=10709File:Plasma mobile.png2021-06-13T19:23:52Z<p>JerseyDevil: source: https://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png
from page: https://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil</p>
<hr />
<div>== Summary ==<br />
source: https://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
<br />
from page: https://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil<br />
== Licensing ==<br />
{{subst:Unknown_copyright}}</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=File:Nemo_mobile.png&diff=10706File:Nemo mobile.png2021-06-13T19:13:48Z<p>JerseyDevil: source: https://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png
from page: https://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil</p>
<hr />
<div>== Summary ==<br />
source: https://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
<br />
from page: https://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil<br />
== Licensing ==<br />
{{subst:Unknown_copyright}}</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil&diff=10702Project Don't be evil2021-06-12T21:51:00Z<p>JerseyDevil: micoSD to microSD (x1), imgs 500 to 200px</p>
<hr />
<div>= The Project "Don't be evil" - Phase 2 of PINE64 Smartphone "PinePhone" Development Kit =<br />
<br />
Project Don't be evil is an actual smartphone developer kit for the PINE64 Smartphone dubbed "PinePhone". It is used in the early stages of development as a starting point for affiliated projects. <br />
PinePhone development has been broken down into three distinct phases: <br />
* First phase - Project Anakin <br />
* Second phase - purpose-built development kit code named "Don't be evil" and introduced at FOSDEM 2019 <br />
* Lastly, the third phase which is the PinePhone itself - scheduled to be prototype released in Q3 2019 and BTO batch released with mobile OS parents in Q4 2019 (pending on software development).<br />
<br />
[[Image:Qee3ovj.jpg|200px]]<br />
[[Image:Qsud2Gt.jpg|200px]]<br />
[[Image:Martijnpocket.jpg|200px]]<br />
<br />
= Project Don't be evil, Baseboard and SOPine Module Information, and Schematics =<br />
* Baseboard Dimensions: 165mm x 76mm x 19.5mm<br />
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, USB type-C connector<br />
* Baseboard Schematic:<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit%20Board%20Structure.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Structure]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.1.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.1 Schematic]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone%20Dev%20Kit%20Ver%201.1_PCB.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.1 PCB Artwork]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.2.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.2 Schematic]<br />
** [https://files.pine64.org/doc/PinePhone/Pinephone%20Dev%20Kit%20Ver%201.2_PCB.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Ver 1.2 PCB Artwork]<br />
* SOPine Module Schematic:<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<br />
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]<br />
* Wifi/BT module information:<br />
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]<br />
* [https://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)]<br />
<br />
<br />
= SoC and Memory Specification =<br />
* Based on Allwinner A64/R18<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
[[File:Allwinner_A64.jpg]] [[File:Allwinner_R18.png]]<br />
<br />
== CPU Architecture ==<br />
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]<br />
* A power-efficient ARM v8 architecture<br />
* 64 and 32bit execution states for scalable high performance<br />
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function<br />
* Support Large Physical Address Extensions(LPAE)<br />
* VFPv4 Floating Point Unit<br />
* 32KB L1 Instruction cache and 32KB L1 Data cache<br />
* 512KB L2 cache<br />
<br />
== GPU Architecture ==<br />
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]<br />
* Support OpenGL ES 2.0 and OpenVG 1.1 standard<br />
<br />
== System Memory ==<br />
* RAM Memory Variants: 2GB LPDDR3.<br />
* Storage Memory: SPI Flash and optional eMMC module from 16GB up to 64GB<br />
<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Allwinner A64/R18 SoC information:<br />
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.''' <br />
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]<br />
* X-Powers AXP803 PMU (Power Management Unit) information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]<br />
* '''Project Don't be evil module/component related information:'''<br />
** 2MPixel front CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC20355Mp-module_for_pinephone_devkit.pdf 2MP CMOS Image Sensor Module Drawing]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC2035%20Product%20Brief.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Product Brief]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/GC2035%20DataSheet.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Datasheet]<br />
** 5MPixel Rear CMOS Camera module information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/ATK-OV5640-5Mp-module_for_pinephone_devkit.pdf 5MP CMOS Image Sensor Module Drawing]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OmniVision OV5640 5MP CMOS Image Sensor Datasheet]<br />
*** [https://www.arducam.com/downloads/modules/OV5640/OV5640_Software_app_note_parallel.pdf OmniVision OV5640 5MP CMOS Image Sensor Software Application Note]<br />
** LCD Touch Screen Panel information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" 1440x720 IPS LCD Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/JD9365D_DS_Preliminary_V0.01_20170427.pdf fiti JD9365D LCD Controller Datasheet]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" Front Panel Touch Screen Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/FT6336GU_Upgrade_Spec_Ver1.0.pdf FocalTech FT6336GU Front Panel Touch Screen Specification]<br />
** Lithium Battery information:<br />
*** [https://files.pine64.org/doc/datasheet/pinephone/ncr18650b.pdf Panasonic NCR18650B 3350mAH Lithium Ion Battery Specification]<br />
** Ethernet PHY information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver]<br />
** Wifi/BT module information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** LTE module information:<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf Quectel EG25-G LTE Module Specification]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25&EC21_QuecCell_AT_Commands_Manual_V1.1.pdf Quectel EC25 LTE Module AT Cammands Set Manual]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Reference_Design_Rev.D_20161111.pdf Quectel EC25 LTE Module Reference Design Guide]<br />
** Sensors:<br />
*** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]<br />
*** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS Datasheet]<br />
*** [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]<br />
<br />
<br />
<br />
<br />
<br />
= Software and OS Image Downloads =<br />
<br />
<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
== Postmarket OS Early Alpha test build [microSD Boot] ==<br />
* Suitable for PinePhone "Don't Be Evil" Dev Kit version 1.1 and version 1.2<br />
* There are two type of LCD panels. For long touch screen cable, please use the build with inverted wording.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://images.postmarketos.org/pinephone/ Direct download from postmarketOS image site]<br />
** [https://wiki.postmarketos.org/wiki/Pine_Don%27t_be_evil_devkit_(pine-dontbeevil) postmarketOS PinePhone "Don't Be Evil" dev kit wiki site]<br />
<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
<br />
== UBPorts mainline build ==<br />
* [https://ci.ubports.com/job/rootfs-pinephone/ UBPorts Jenkins for PinePhone]<br />
<br />
The link above seems to be broken, if so try this:<br />
[https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ Jenkins Project rootfs-pinephone]<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
<br />
== KDE Plasma Mobile build ==<br />
* Not Yet Ready *<br />
<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
<br />
== Sailfish OS build ==<br />
<br />
The Sailfish OS image is build on Gitlab CI, the latest image can be installed using our [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script] written in Bash.<br />
<br />
The script downloads the image and bootloader from our CI, extracts everything and burns it onto the SD card.<br />
<br />
'''Instructions:'''<br />
<br />
1. Download the flashing script<br />
<br />
2. Insert a microSD card in your device<br />
<br />
3. Make the script executable: <code>chmod +x flash-it.sh</code><br />
<br />
4. Execute it: <code>./flash-it.sh</code><br />
<br />
5. Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).<br />
<br />
'''Note''': The script will format and flash the SD card, make sure that you don't have any important data on the SD card!<br />
<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
== Maemo Leste build ==<br />
* Works on dev kit versions 1.1 and 1.2 <br />
* DD image to a micro SD (8GB+) or eMMC <br />
** [https://maedevu.maemo.org/images/pinephone-dontbeevil/ Maemo Leste test builds download]<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
== NixOS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
<br />
== LuneOS build ==<br />
* [https://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone and thanks to Tofe]<br />
* Tofe recommends using bmaptool ; for example "bmaptool copy https://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0" <br />
<br />
<br />
https://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
<br />
== Nemo Mobile build ==<br />
* Not Yet Ready *<br />
<br />
= Mali-400 64-bit Driver =<br />
<br />
== Mali-400 64-bit Driver [20171220] ==<br />
* [[Mali_Driver|Mali 64-bit X11 and Wayland Driver Download]]<br />
<br />
<br />
== Quick Links to Build Sources of OS Images ==<br />
<br />
* [https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix A64 mainline status matrix chart]<br />
<br />
'''Some these OS images labelled as <span style="color:#FF0000">beta or nightly builds</span> which means they are only fit for testing purposes<br />
<br />
'''These images should be <span style="color:#FF0000">used at your own risk</span> and are not fit for normal use'''<br />
<br />
* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]<br />
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]<br />
<br />
<br />
= Errata for ver1.1 and ver1.2 board =<br />
<br />
'''1. Please DON'T insert micro SIM card to dev kit board micro SIM card slot, the SIM data, VPP, and GND signal have been misplaced. A miciPCIe adapter with sim card holder 9shown as below photo) will be provide to developers to correct this mistake.'''<br />
<br />
[[File:MiniPCIe_with_sim_slot_adapter.png]]<br />
<br />
<br />
'''2. The PinePhone dev kit doesn't charge due to VBUS on SOPine module is not connected. Please connect R9688 solder pads with 0 ohm resistor or using thin wire bridge up the solder pads. Location shows as below:'''<br />
<br />
[[File:PinePhone_VBUS_charging_small.png]]<br />
<br />
<br />
'''3. The SOPINE's SPI NOR flash storage and the devkit's camera flash (heh) share the same GPIO pins. The flash storage may not be used.'''<br />
<br />
[[File:SOPINE-SPI-Flash.png]] [[File:Pinephone-1.1-flash-schematic.png]]<br />
<br />
<br />
'''4. On the camera flash GPIO conflict, the new assignment of GPIO PB3 pin for SGM3140 FLASH_EN and GPIP PD7 for FLASH_TRIGOUT. Please note that PD7 is also LCD_ID pin which may not be used.'''<br />
<br />
[[File:GPIO_PB3_location.jpg|200px]]<br />
GPIO PB3 location<br />
<br />
[[File:U54_SGM3140_FLASH_EN pin location.jpg|200px]]<br />
U54 SGM3140 FLASH_EN pin location<br />
<br />
[[File:Flash_GPIO_Reassigned.jpg|200px]]<br />
Flash GPIOs Reassigned wiring<br />
<br />
<br />
<br />
= Other Resources =<br />
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]<br />
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]<br />
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]<br />
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]<br />
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]<br />
* [https://osmocom.org/projects/quectel-modems/wiki/EC25/24 Quectel EC-25 LTE module open source information]<br />
<br />
[[Category:PinePhone]] [[Category:Allwinner A64]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PineCube&diff=10701PineCube2021-06-12T21:49:24Z<p>JerseyDevil: micoSD to microSD (x1)</p>
<hr />
<div>{{under construction}}<br />
<br />
== Specifications ==<br />
* '''Dimensions:''' 55mm x 51mm x 51.5mm<br />
* '''Weight:''' 55g<br />
* '''Storage:'''<br />
** MicroSD slot, bootable<br />
** 128Mb SPI Nor Flash, bootable<br />
* '''Cameras:''' OV5640, 5Mpx <br />
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz<br />
* '''RAM:''' 128MB DDR3<br />
* '''I/O:'''<br />
** 10/100Mbps Ethernet with passive PoE (''4-18V!'')<br />
** USB 2.0 A host<br />
** 26 pins GPIO port<br />
*** 2x 3.3V Ouptut<br />
*** 2x 5V Output<br />
*** 1x I2C<br />
*** 2x UART<br />
*** 2x PWM<br />
*** 1x SPI<br />
*** 1x eMMC/SDIO/SD (8-bit)<br />
*** 6x Interrupts<br />
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''<br />
** Internal microphone<br />
* '''Network:'''<br />
** WiFi<br />
* '''Screen:''' optional 4.5" RGB LCD screen<br />
* '''Misc. features:''' <br />
** Volume and home buttons<br />
** Speakers and Microphone<br />
* '''Power DC in:'''<br />
** 5V 1A from MicroUSB Port or GPIO port<br />
** 4V-18V from Ethernet passive PoE<br />
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]<br />
<br />
== PineCube board information, schematics and certifications ==<br />
* PineCube mainboard schematic:<br />
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]<br />
* PineCube faceboard schematic:<br />
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]<br />
* PineCube certifications:<br />
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]<br />
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]<br />
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]<br />
<br />
<br />
<br />
== Datasheets for components and peripherals ==<br />
* Allwinner (Sochip) S3 SoC information:<br />
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]<br />
<br />
* X-Powers AXP209 PMU (Power Management Unit) information:<br />
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]<br />
<br />
* CMOS camera module information:<br />
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]<br />
<br />
* LCD touch screen panel information:<br />
<br />
* Lithium battery information:<br />
<br />
* WiFi/BT module information:<br />
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]<br />
<br />
* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML]) (Pin1 is marked on the board by a white dot on the PCB)<br />
[[File:PineCube_GPIO_Pinout.png|700px]]<br />
<br />
<br />
* Case information:<br />
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PineCube ( china not open source file) 3D file]<br />
** [https://drive.google.com/file/d/1MDNxnPL2kuYGC4Y4qf9J6YPYZF15KnN7/view?usp=sharing Quick and dirty STL conversion (beta) by doodlebro. Prints and fits at 0.25mm layer height.]<br />
<br />
[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]<br />
<br />
== Operating Systems ==<br />
<br />
=== Mainlining Efforts ===<br />
<br />
Please note:<br />
<br />
* this list is most likely not complete<br />
* no review of functionality is done here, it only serves as a collection of efforts<br />
<br />
{| class="wikitable"<br />
!colspan="3"|Linux kernel<br />
|-<br />
| Type<br />
| Link<br />
| Available in version<br />
|-<br />
| Devicetree Entry Pinecube<br />
| https://lkml.org/lkml/2020/9/22/1241<br />
| 5.10<br />
|-<br />
| Correction for AXP209 driver<br />
| https://lkml.org/lkml/2020/9/22/1243<br />
| 5.9<br />
|-<br />
| Additional Fixes for AXP209 driver<br />
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/<br />
| tdb (5.11?)<br />
|-<br />
| Device Tree Fixes<br />
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/<br />
| 5.10<br />
|-<br />
!colspan="3"|U-boot<br />
|-<br />
| Type<br />
| Link<br />
| Available in version<br />
|-<br />
| PineCube Board Support<br />
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044<br />
| expected in v2021.01<br />
|-<br />
!colspan="3"|Buildroot<br />
|-<br />
| No known mainlining efforts yet<br />
|<br />
|<br />
|}<br />
<br />
<br />
=== NixOS ===<br />
<br />
* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]<br />
<br />
<br />
<br />
=== Buildroot ===<br />
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.<br />
<br />
This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.<br />
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.<br />
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.<br />
<br />
=== Armbian ===<br />
<br />
The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.<br />
<br />
<br />
==== Armbian Build Image with motion [microSD Boot] [20201222] ====<br />
* Armbian Ubuntu Focal build for the Pinecube with the motion (detection) package preinstalled.<br />
* There are 2 ways to interact with the OS:<br />
** Scan for the the device IP (with hostname pinecube)<br />
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER to login to the serial console, then check for assigned IP<br />
* DD image (for 8GB microSD card and above)<br />
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]<br />
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b<br />
*** File Size: 328MGB<br />
<br />
[https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 GitHub gist] for the userpatch which pre-installs and configures the motion (detection) package. <br />
<br />
Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.<br />
Although [https://www.armbian.com/download/?device_support=No+official+support+(CSC) not officially supported] it enables the usage of Debian and Ubuntu.<br />
<br />
A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian (login: root, password: 1234).<br />
<br />
Motion daemon can be enabled using systemctl (With root) <code>systemctl enable motion</code>. Then just reboot.<br />
<br />
==== Serial connection using screen and the woodpecker USB serial device ====<br />
<br />
First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.<br />
<br />
On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:<br />
<br />
<code>screen /dev/ttyUSB0 115200</code><br />
<br />
==== Serial connection using screen and Arduino Uno ====<br />
<br />
You can use the Arduino Uno or other Arduino boards as a USB serial device.<br />
<br />
First you must either remove the microcontroller from it's socket, or if your Arduino board does not allow this, then you can use wires to jump RESET (RST) and GND to isolate the SOC.<br />
<br />
After this you can either use the Arduino IDE and it's Serial monitor after selecting your <code>/dev/ttyACMx</code> Arduino device, or screen:<br />
<br />
<code>screen /dev/ttyACM0 115200</code><br />
<br />
[[File:ArduinoSerialPinecube.jpg|400px]]<br />
<br />
==== Serial connection using pinephone/pinebook pro serial debugging cable ====<br />
<br />
You can use the [https://wiki.pine64.org/wiki/PinePhone#Serial_console serial console] USB cable for pinephone and pinebook pro at the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ store]. With a [https://www.amazon.com/3-5mm-Stereo-Female-terminal-connector/dp/B077XPSKQD female terminal block] wire using breadboard wire into the GPIO block at the following locations in a "null modem" configuration with transmit and receive crossed between your computer and the pinecube:<br />
<br />
S - Ground (to pin 9)<br />
R - Transmit (to pin 8)<br />
T - Receive (to pin 10)<br />
<br />
From Linux you can access the console of the pinecube using the screen command:<br />
<br />
<code>screen /dev/ttyUSB0 115200</code><br />
<br />
==== Basic bandwidth tests with iperf3 ====<br />
<br />
Install armbian-config:<br />
<code>apt install armbian-config</code><br />
<br />
Enable iperf3 through the menu in armbian-config:<br />
<code>armbian-config</code><br />
<br />
On a test computer on the same network segment run iperf3 as a client:<br />
<code>iperf3 -c pinecube -t 60</code><br />
<br />
The same test computer, run iperf3 in the reverse direction:<br />
<code>iperf3 -c pinecube -t 60 -R</code><br />
<br />
=== Performance results ===<br />
<br />
==== Wireless network performance ====<br />
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.<br />
<br />
Client rate for sixty seconds:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender<br />
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver<br />
<br />
<br />
Client rate with -R for sixty seconds:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender<br />
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver<br />
<br />
Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.<br />
<br />
Client rate for sixty seconds with WireGuard:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender<br />
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver<br />
<br />
Client rate with -R for sixty seconds with WireGuard:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender<br />
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver<br />
<br />
====== Wired network performance ======<br />
<br />
The Ethernet network does not work in the current Ubuntu Focal Armbian image or the Ubuntu Groovy Armbian image.<br />
<br />
The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.<br />
<br />
Client rate for sixty seconds:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender<br />
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver<br />
<br />
Client rate with -R for sixty seconds:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender<br />
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver<br />
<br />
Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.<br />
<br />
Client rate for sixty seconds with WireGuard:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender<br />
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver<br />
<br />
Client rate with -R for sixty seconds with WireGuard:<br />
<br />
[ ID] Interval Transfer Bitrate Retr<br />
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender<br />
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver<br />
<br />
== Streaming the camera to the network ==<br />
<br />
In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10). See [https://github.com/ioerror/pinecube this small project for the pinecube] for easy to use programs tuned for the PineCube.<br />
<br />
In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!<br />
<br />
=== gstreamer: h264 HLS ===<br />
<br />
HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).<br />
<br />
HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.<br />
<br />
Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:<br />
<br />
<code>mkdir /dev/shm/hls/</code><br />
<br />
Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).<br />
<br />
In one terminal, run the camera capture pipeline:<br />
<code><br />
cd /dev/shm/hls/ && <br />
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' && <br />
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3<br />
</code><br />
<br />
Alternatively it is possible to capture at a higher resolution:<br />
<code><br />
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'<br />
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3<br />
</code><br />
<br />
In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:<br />
<code><br />
cd /dev/shm/hls/ && python3 -m http.server<br />
</code><br />
<br />
Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.<br />
<br />
It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.<br />
<br />
You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code><br />
<br />
Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)<br />
<br />
To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.<br />
<br />
It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!<br />
<br />
=== v4l2rtspserver: h264 RTSP ===<br />
<br />
Install dependencies:<br />
<br />
apt install -y cmake gstreamer1.0-plugins-bad gstreamer1.0-tools \<br />
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \<br />
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \<br />
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \<br />
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \<br />
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \<br />
libvpx-dev libx264-dev libjpeg-dev libx265-dev linux-headers-dev-sunxi;<br />
<br />
Install kernel source and build v4l2loopback module:<br />
<br />
apt install linux-source-5.11.3-dev-sunxi64 #Adjust kernel version number to match current installation with "uname -r"<br />
cd /usr/src/v4l2loopback-0.12.3; make && make install && depmod -a<br />
<br />
Build required v4l2 software:<br />
<br />
git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;<br />
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;<br />
<br />
Running the camera:<br />
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';<br />
modprobe v4l2loopback video_nr=10 debug=2;<br />
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &<br />
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10<br />
<br />
Note that you might get an error when running media-ctl indicating that the resource is busy. This could be because of the motion program that runs on the stock OS installation. Check and kill any running /usr/bin/motion processes before running the above steps.<br />
<br />
The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.<br />
<br />
You'll probably see about a 2-3s lag with this approach, possibly due to the H264 compression and the lack of hardware acceleration at the moment.<br />
<br />
=== gstreamer: JPEG RTSP ===<br />
<br />
GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/<br />
<br />
After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code><br />
<br />
This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.<br />
<br />
=== gstreamer: h264 RTSP ===<br />
<br />
Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.<br />
<br />
=== gstreamer: JPEG RTP UDP ===<br />
<br />
Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code><br />
<br />
Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000</code><br />
<br />
Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code><br />
<br />
Note that the sender must specify the recipient's IP address in place of <code>$client_ip</code>; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see <code>gst-inspect-1.0 udpsrc</code> and <code>gst-inspect-1.0 udpsink</code> for details.)<br />
<br />
=== gstreamer: JPEG RTP TCP ===<br />
<br />
Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code><br />
<br />
Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code><br />
<br />
Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code><br />
<br />
=== gstreamer and socat: MJPEG HTTP server ===<br />
<br />
This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.<br />
<br />
This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). Compared to HLS, it has the disadvantages that MJPEG requires more bandwidth than h264 for similar quality, pause and seek are not possible, stalled connections cannot jump ahead when they are unstalled, and, in the case of this primitive implementation, it only supports one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)<br />
<br />
Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.<br />
<br />
Create a file called <code>mjpeg-response.sh</code>:<br />
#!/bin/bash<br />
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'<br />
b="--duct_tape_boundary"<br />
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"<br />
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null<br />
<br />
Make it executable: <code>chmod +x mjpeg-response.sh</code><br />
<br />
Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code><br />
<br />
And browse to http://pinecube.local:8080/ in your browser.<br />
<br />
=== virtual web camera: gstreamer, mjpeg, udp rtp unicast ===<br />
<br />
It's possible to set up the pinecube as a virtual camera video device (Video 4 Linux) so that you can use it with video conferencing software, such as Jitsi Meet. Note that this has fairly minimal (<1s) lag when tested on a wired 1Gb ethernet network connection and the frame rate is passable. MJPEG is very wasteful in terms of network resources, so this is something to keep in mind. The following instructions assume Debian Linux (Bullseye) as your desktop machine, but could work with other Linux OSes too. It's possible that someday a similar system could work with Mac OS X provided that someone writes a gstreamer plugin that exposes a Mac OS Core Media DAL device as a virtual webcam, like they did [https://github.com/johnboiles/obs-mac-virtualcam here] for OBS.<br />
<br />
First, you will need to set up the pinecube with gstreamer much like the above gstreamer, but in 1280x720 resolution. Also, you will be streaming to the desktop machine using UDP, with IP address represented by $desktop below at UDP port 8000.<br />
<br />
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]'<br />
gst-launch-1.0 v4l2src device=/dev/video0 ! image/jpeg,width=1280,height=720,framerate=30/1 ! rtpjpegpay name=pay0 ! udpsink host=$desktop port=8000<br />
<br />
On your desktop machine, you will need to install the gstreamer suite and the special v4l2loopback kernel module to bring the mjpeg stream to the Video 4 Linux device /dev/video10.<br />
<br />
sudo apt install gstreamer1.0-tools gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly v4l2loopback-dkms<br />
sudo modprobe v4l2loopback video_nr=10 max_buffers=32 exclusive_caps=1 # Creates /dev/video10 as a virtual v4l2 device, allocates increased buffers and exposes exclusive capabilities for chromium to find the video device<br />
gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26,framerate=30/1 ! rtpjpegdepay ! jpegdec ! video/x-raw, format=I420, width=1280, height=720 ! autovideoconvert ! v4l2sink device=/dev/video10<br />
<br />
The most common error found when launching the gstreamer pipeline above is the following error message, which seems to happen when the [https://github.com/umlaeute/v4l2loopback/issues/174 max_buffers aren't set] on the v4l2loopback module (see above), or if there is a v4l client (vlc, chromium) already connected to /dev/video10 when starting the pipeline. There does seem to be a small level of instability in this stack that could be improved.<br />
<br />
gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:<br />
streaming stopped, reason not-negotiated (-4)<br />
<br />
Now that you have /dev/video10 hooked into the gstreamer pipeline you can then connect to it using VLC. VLC is a good local test that things are working. You can view the stream like this. Note that you could do the same thing with mpv/ffmpeg, but there are [https://www.raspberrypi.org/forums/viewtopic.php?t=270023 problems] currently.<br />
<br />
vlc v4l2:///dev/video10<br />
<br />
Be sure to disconnect vlc before trying to use the virtual web camera with chromium. Launch chromium and go to a web conference like [https://meet.jit.si jitsi]. When it prompts you for the camera pick the "Dummy Video Device..." and it should be much like what you see in vlc. Note that firefox isn't really working at this moment and the symptoms appear very similar to the problem with mpv/ffmpeg mentioned above, ie. when they connect to the camera they show only the first frame and then drop. It's unclear whether the bug is in gstreamer, v4l, or ffmpeg (or somewhere in these instructions).<br />
<br />
== Debugging camera issues with the gstreamer pipeline ==<br />
<br />
If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.<br />
<br />
If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:<br />
<pre><br />
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy<br />
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy<br />
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy<br />
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy<br />
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy<br />
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy<br />
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy<br />
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy<br />
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy<br />
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy<br />
</pre><br />
<br />
== Camera Adjustments ==<br />
<br />
=== Low light mode ===<br />
<br />
To get imagery in low-light conditions you can turn on the infrared LED's to light up the dark area and also enable the IR cut filter using the commands below. Note that these were performed on Armbian using the instructions from here [https://github.com/danielfullmer/pinecube-nixos#enablingdisabling-ir-cut-filter].<br />
<br />
<pre><br />
# Run these as root<br />
<br />
# Turn on the IR LED lights (note that you can see a faint red glow from them when it's low light)<br />
# Turn them off with echo 1 instead<br />
# echo 0 > /sys/class/leds/pine64\:ir\:led1/brightness<br />
# echo 0 > /sys/class/leds/pine64\:ir\:led2/brightness<br />
<br />
# Export gpio, set direction<br />
# echo 45 > /sys/class/gpio/export<br />
# echo out > /sys/class/gpio/gpio45/direction<br />
<br />
# Enable IR cut filter (note that you can hear the switching noise)<br />
# Disable with echo 0 instead<br />
# echo 1 > /sys/class/gpio/gpio45/value<br />
</pre><br />
<br />
== SDK ==<br />
<br />
==== Stock Linux ====<br />
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]<br />
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8<br />
** File Size: 3.50GB<br />
===== How to compile =====<br />
<br />
You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]<br />
<br />
====== On a dedicated machine ======<br />
<br />
Recommended system requirements:<br />
* OS: (L)Ubuntu 16.04<br />
* CPU: 64-bit based<br />
* Memory: 8 GB or higher<br />
* Disk: 15 GB free hard disk space<br />
<br />
'''Install required packages'''<br />
<pre><br />
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev<br />
</pre><br />
'''Install older Make 3.82 and Java JDK 6'''<br />
<pre><br />
pushd /tmp<br />
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz<br />
tar xfv make-3.82.tar.gz<br />
cd make-3.82<br />
./configure<br />
make<br />
sudo apt purge -y make<br />
sudo ./make install<br />
cd ..<br />
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)<br />
chmod +x jdk-6u45-linux-x64.bin <br />
./jdk-6u45-linux-x64.bin <br />
sudo mkdir /opt/java/<br />
sudo mv jdk1.6.0_45/ /opt/java/<br />
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1<br />
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1<br />
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1<br />
sudo update-alternatives --config javac<br />
sudo update-alternatives --config java<br />
sudo update-alternatives --config javaws<br />
popd<br />
</pre><br />
'''Unpack SDK and then compile and pack the image'''<br />
<pre><br />
7z x 'PineCube Stock BSP-SDK ver1.0.7z'<br />
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk<br />
cd pinecube-sdk/camdroid<br />
source build/envsetup.sh<br />
lunch<br />
mklichee<br />
make -j3<br />
pack<br />
</pre><br />
<br />
====== Using Vagrant ======<br />
<br />
You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.<br />
<br />
Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]<br />
<br />
After spinning up the VM, you just need to run the build:<br />
<pre><br />
cd pinecube-sdk/camdroid<br />
source build/envsetup.sh<br />
lunch<br />
mklichee<br />
make -j3<br />
pack<br />
</pre><br />
<br />
<br />
== Community Projects ==<br />
<br />
Share your project with a PineCube here!<br />
<br />
<br />
[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=SOEDGE&diff=10700SOEDGE2021-06-12T21:45:17Z<p>JerseyDevil: micoSD to microSD (x1)</p>
<hr />
<div>The SOEdge is a 3TOPS compute module that can be paired with the SOPine base board or USB 3.0 and PCIe adapters for development. It can connect to a SBC, such as the ROCKPro64 or a regular PC. <br />
<br />
== Software and OS Image Downloads ==<br />
=== SOEdge Software Release ===<br />
<br />
The SOEdge software releases can be found in the article [[SOEdge Software Release]].<br />
<br />
== Accessories Step-by-Step Guides ==<br />
Under [[Accessories_Step_by_Step_Guides|'Guides for model A baseboard accessories']] you can find instructions and guides concerning:<br />
* Enclosures<br />
* Bluetooth and WiFi module<br />
* Real Time Clock (RTC) battery<br />
* Real Time Clock (RTC) battery holder<br />
* First and third party cases<br />
* Featured 3D printed cases (and more)<br />
<br />
== SoC and Memory Specification ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK18_Series/2019/0529/989.html Rockchip RK1808]<br />
[[File:RK1808_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a35 Dual-core ARM Cortex-A35 Processor@1600-2000Mhz]<br />
* A power-efficient ARM 64-Bit Armv8-A architecture<br />
* AArch32 for full backward compatibility with Armv7<br />
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function<br />
* Support Large Physical Address Extensions(LPAE)<br />
* VFPv4 Floating Point Unit<br />
* 32KB L1 Instruction cache and 32KB L1 Data cache<br />
* AArch64 for 64-bit support and new architectural features<br />
* TrustZone security technology<br />
* Neon Advanced SIMD<br />
* DSP and SIMD extensions<br />
* VFPv4 Floating point<br />
* Hardware virtualization support<br />
* 128KB L2 cache<br />
<br />
<br />
=== Neural Process Unit NPU Capability ===<br />
* [https://www.verisilicon.com/en/IPPortfolio/VivanteNPUIP NPU IP from Verisilicon Vivante]<br />
* Support max 1920 Int8 MAC operation per cycle<br />
* Support max192 Int16 MAC operation per cycle<br />
* Support max 64 FP16 MAC operation per cycle<br />
* 512KB internal buffer<br />
* One isolated voltage domain to support DVFS<br />
* [https://github.com/VeriSilicon/acuity-models Acuity models Github]<br />
<br />
[[File:Vivante_Acuity_SDK.jpg]]<br />
<br />
=== System Memory ===<br />
* RAM Memory Variants: 2GB DDR4.<br />
* Storage Memory: 128Mb SPI Flash and optional eMMC module from 16GB up to 128GB<br />
<br />
== SOEdge Baseboard Features ==<br />
<br />
=== Network ===<br />
* 10/100/1000Mbps Etherne<br />
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)<br />
<br />
=== Storage ===<br />
* microSD - bootable, support SDHC and SDXC, storage up to 256GB<br />
* USB - 2 USB2.0 Host port<br />
<br />
=== Expansion Ports ===<br />
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P<br />
* TP - Touch Panel Port, SPI with interrupt<br />
* RTC - Real Time Clock Battery Connector<br />
* VBAT - Lithium Battery Connector with temperature sensor input<br />
* Wifi/BT Module Header - SDIO 3.0 and UART<br />
* 2x20 pins "Pi2" GPIO Header<br />
* PCIe 2x open ended slot<br />
<br />
== SOEdge Module and Baseboard Information, Schematics, and Certifications ==<br />
* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm<br />
* Input Power: DC 12V @ 3A 5.5OD/2.1ID Barrel DC Jack connector<br />
<br />
* SOEdge Module Schematic:<br />
** [https://files.pine64.org/doc/SOEdge/SOEdge-Schematic-v2.0-190919.pdf SOEdge Module ver 2.0 20190919 Schematic]<br />
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Top PDF file]<br />
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom PDF file]<br />
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Top Drawing file]<br />
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom Drawing file]<br />
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.xlsx SOEdge Module Pin Assignment ver 1.0 in Excel format(includes comparison chart to SOPine)]<br />
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.ods SOEdge Module Pin Assignment ver 1.0 in Open Document format(includes comparison chart to SOPine)]<br />
* SOEdge Model "A" Baseboard Schematic and PCB Board Resource:<br />
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_Schematic-20210223.pdf SOEdge Model "A" Baseboard Schematic 20210223 PDF file]<br />
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_PCB-TOP-20210223.pdf SOEdge Model "A" Baseboard 20210223 PCB Component Placement Top PDF file]<br />
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_PCB-BOT-20210223.pdf SOEdge Model "A" Baseboard 20210223 PCB Component Placement Bottom PDF file]<br />
* SOEdge Neural AI Stick Schematic:<br />
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Neural%20AI%20Stick%20Schematic_V10.pdf SOEdge Neural AI Stick PDF file]<br />
* SOEdge/SOPine/PINE A64 Wifi/BT module Schematic<br />
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]<br />
* SOEdge module together with model "A" baseboard Certification:<br />
** Disclaimer: Please note that SOEdge module is not a "final" product and in general certification is not necessary. However, SOEdge module still submits the mpdel A baseboard for FCC, CE, and ROHS certifications and obtain the certificates to prove that can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK1808 SoC information:<br />
** [http://opensource.rock-chips.com/images/4/43/Rockchip_RK1808_Datasheet_V1.2_20190527.pdf Rockchip RK1808 ver 1.2 datasheet]<br />
** [https://files.pine64.org/doc/datasheet/SOEdge/Rockchip%20RK1808%20TRM%20Part1%20V1.2--20190826%20open%20source.pdf Rockchip TK1808 Technical Reference Manual Part 1]<br />
* Rockchip RK809 PMU (Power Management Unit) information:<br />
** [https://rockchip.fr/RK809%20datasheet%20V1.01.pdf Rockchip RK809 PMIC Datasheet]<br />
* DDR4 information:<br />
** [https://files.pine64.org/doc/datasheet/SOEdge/Micron%208Gb_DDR4_SDRAM.pdf Micron DDR4 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]<br />
* '''SOEdge Related:'''<br />
** LCD Touch Screen Panel information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]<br />
** Ethernet PHY information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for SOEdge model A baseboard]<br />
** Wifi/BT module information:<br />
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf SOEdge/SOPine/PINE A64 Wifi/BT Module Schematic]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** Enclosure information:<br />
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]<br />
*** [https://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]<br />
*** [https://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]<br />
** Connector information:<br />
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]<br />
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]<br />
<br />
== SOEdge/SOPine Cluster Board Resource ==<br />
* Cluster board is an hardware open source project and will be available at PINE64 store on late January 2018. <br />
* Please note that this project is not "OSH" compliance.:<br />
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.DSN Clusterboard version 2.2 Schematic Capture source file]<br />
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_Schematic.pdf Clusterboard version 2.2 Schematic Capture PDF file]<br />
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.brd Clusterboard version 2.2 PCB Job source file]<br />
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD%20V2.2-gerber.rar Clusterboard version 2.2 PCB Gerber file]<br />
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_PCB.pdf Clusterboard version 2.2 PCB Layout PDF file]<br />
** [https://files.pine64.org/doc/clusterboard/clusterboard_20pins_header.jpg Clusterboard 20pins header definition]<br />
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd96840f4ec37c60bcf12 Clusterboard 3D drawing in Fusion360]<br />
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd968cd6bc203ac753401?viewState=NoIgbgDAdAjCA0ICGBmARgEwGZIOwGMBaDFADgFNCAWfAJi2o1IFZDmlTSIA2DW8-FTQgAukA Clusterboard PDF drawing]<br />
<br />
<br />
= Linux Image Releases =<br />
<br />
<br />
== Stock BSP ==<br />
<br />
=== BSP Linux ver 1.1 Build from SDK ===<br />
* Please unzip first and then using Rockchip tool to flash in<br />
* [https://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]<br />
** [http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz download from pine64.org]<br />
** MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9<br />
** File Size: 119MB<br />
<br />
=== BSP Linux ver 1.1 Build as USB Stick application from SDK ===<br />
* Please unzip first and then using Rockchip tool to flash in<br />
* [https://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]<br />
** [http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz download from pine64.org]<br />
** MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30<br />
** File Size: 47MB<br />
<br />
<br />
== Factory Test Build ==<br />
<br />
* Factory Test Build by Gamiee<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [http://files.pine64.org/os/SOEdge/gamiee/update-soedge-factory-test-2021-03-23.img.gz download from pine64.org]<br />
** MD5 (GZip file): b3d09933734eaaebb34c357b73f5c69e<br />
** File Size: 119MB<br />
<br />
<br />
<br />
= Linux BSP SDK =<br />
<br />
== Linux BSP Kernel ver 1.1 ==<br />
* [http://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_SDK_v1.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): a66c92e52824762d7c0a63400d6342ea<br />
** File Size: 13.55GB<br />
<br />
== Linux BSP Kernel ver 1.1 as USB Stick application ==<br />
* [http://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_USB_Dongle_SDK_v1.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 46f12441e8c35c06184681f355c89651<br />
** File Size: 9.65GB<br />
<br />
<br />
== Other Resources ==<br />
<br />
<br />
<br />
[[Category:SOPine]] [[Category:Rockchip RK1808]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=Pinebook_Software_Releases&diff=10699Pinebook Software Releases2021-06-12T21:44:42Z<p>JerseyDevil: micoSD to microSD (x3)</p>
<hr />
<div>= Linux Image Releases =<br />
<br />
'''Special thanks to Sunxi community, ayufan, and longsleep for their contributions'''<br />
<br />
Below you will find useful links to various resources and forum threads:<br />
* [https://linux-sunxi.org/Pine_Pinebook Sunxi Pinebook Page]<br />
<br />
==Manjaro ARM==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
<br />
=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/kde-plasma/ Direct download from osdn.net]<br />
<br />
=== Manjaro MATE ARM Community Build Image [microSD / eMMC Boot] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/mate/ Direct download from osdn.net]<br />
<br />
=== Manjaro XFCE ARM Community Build Image [microSD / eMMC Boot] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/xfce/ Direct download from osdn.net]<br />
<br />
=== Manjaro I3 ARM Community Build Image [microSD / eMMC Boot] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/i3/ Direct download from osdn.net]<br />
<br />
=== Manjaro SWAY ARM Community Build Image [microSD / eMMC Boot] ===<br />
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/sway/ Direct download from osdn.net]<br />
<br />
<br />
<br />
== Armbian ==<br />
[[File:armbian.png|right|100px]]<br />
<br />
=== Armbian Debian Buster [microSD / eMMC Boot] ===<br />
* Armbian provides a build system and images for Debian/Xenial with BSP kernel and mainline kernel<br />
* DD image (for 8GB microSD card and above)<br />
** [https://dl.armbian.com/pinebook-a64/Buster_legacy_desktop Pinebook Armbian download site]<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-a64/ site].<br />
<br />
=== Armbian Ubuntu Focal XFCE Desktop [microSD / eMMC Boot] ===<br />
* Armbian provides a build system and images for Debian/Xenial with BSP kernel and mainline kernel<br />
* DD image (for 8GB microSD card and above)<br />
** [https://dl.armbian.com/pinebook-a64/Focal_legacy_desktop Pinebook Armbian download site]<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-a64/ site].<br />
<br />
<br />
<br />
== KALI ==<br />
[[File:Kali.jpeg|right|100px]]<br />
<br />
=== KALI Build Image by Defensive Security [microSD / eMMC Boot] [2020.2] ===<br />
* To learn more, please visit the official [https://www.offensive-security.com/kali-linux-arm-images/#2536677610546-d94f090d-c5ea KALI by Defensive Security website]<br />
* DD image (for 8GB microSD card and above)<br />
** [https://images.kali.org/arm-images/kali-linux-2020.4-pinebook.img.xz Direct download from Defensive Security]<br />
*** MD5 (XZ file): 7E3643730D2D287A3726B641A6DA177C<br />
*** File Size: 686MB<br />
* Login with<br />
** username: kali<br />
** password: kali<br />
<br />
<br />
<br />
== AOSC ==<br />
[[File:aosc.png|right|100px]]<br />
<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
* AOSC using LZ4 compression algorithm, please visit the [https://github.com/lz4/lz4 LZ4 github site] for utility<br />
* DD image to eMMC module using USB adapter for eMMC module.<br />
* 8GB microSD card and above or 16GB eMMC module and above<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
=== AOSC KDE Community Build Image [microSD / eMMC Boot] ===<br />
* [https://releases.aosc.io/os-arm64/sunxi64/kde/pinebook/ Direct download from AOSC]<br />
<br />
=== AOSC GNOME Community Build Image [microSD / eMMC Boot] ===<br />
* [https://releases.aosc.io/os-arm64/sunxi64/gnome/pinebook/ Direct download from AOSC]<br />
<br />
=== AOSC MATE Community Build Image [microSD / eMMC Boot] ===<br />
* [https://releases.aosc.io/os-arm64/sunxi64/mate/pinebook/ Direct download from AOSC]<br />
<br />
=== AOSC XFCE Community Build Image [microSD / eMMC Boot] ===<br />
* [https://releases.aosc.io/os-arm64/sunxi64/xfce/pinebook/ Direct download from AOSC]<br />
<br />
=== AOSC LXDE Community Build Image [microSD / eMMC Boot] ===<br />
* [https://releases.aosc.io/os-arm64/sunxi64/lxde/pinebook/ Direct download from AOSC]<br />
<br />
<br />
<br />
== KDE Neon Image ==<br />
[[File:kde_neon.png|right|100px]]<br />
<br />
=== KDE Neon Community Build Image [microSD / eMMC Boot] ===<br />
* DD image (for 8GB microSD card and above)<br />
<br />
** [https://files.kde.org/neon/images/pinebook-remix-nonfree/useredition/ Direct download latest release build from KDE Neon Pinebook and 1080P Pinebook]<br />
* Login with<br />
** username: live<br />
** password: live<br />
<br />
<br />
=== KDE Neon Community Build Image [microSD / eMMC Boot] ===<br />
* DD image (for 8GB microSD card and above)<br />
* For 14.1' and 11.6" Pinebook, please choose "neon-pinebook-remix-useredition-202xxxxx-1500-arm64.img.gz"<br />
* For 1080P 11.6" Pinebook, please choose "neon-pinebook-remix-useredition-202xxxxx-1500-arm64-1080p.img.gz"<br />
** [https://files.kde.org/neon/images/pinebook-remix-nonfree/useredition/ Direct download latest release build from KDE Neon 1080P Pinebook]<br />
<br />
<br />
<br />
== Q4OS ==<br />
[[File:q4os.png|right|100px]]<br />
<br />
=== Q4OS Community Build Image [microSD Boot] ===<br />
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'<br />
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=4506 forum] or official [https://q4os.org/index.html Q4OS website]<br />
* DD image for 14.1" and 11.6" Pinebook (8GB microSD card and above)<br />
** [https://sourceforge.net/projects/q4os/files/stable/ Direct download latest release build from SourceForge and look for q4os-x.x-pinebook.xx.zip]<br />
* DD image for 1080P 11.6" Pinebook (for 8GB microSD card and above)<br />
** [https://sourceforge.net/projects/q4os/files/stable/ Direct download latest release build from SourceForge and look for q4os-x.x-pinebook1080p.xx.zip]<br />
* login with:<br />
** username: adminq<br />
** password: adminq<br />
<br />
<br />
<br />
== DietPi ==<br />
[[File:dietpi.png|right|100px]]<br />
<br />
* DietPi is a '''lightweight''', yet '''easy to setup''' and '''feature-rich''' Linux distribution, based on '''Debian'''.<br />
* To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation].<br />
* Discuss the Pinebook build on the [https://forum.pine64.org/showthread.php?tid=12512 PINE64 forum thread].<br />
* DD image (for 4 GiB micro SD card and above)<br />
** [https://dietpi.com/downloads/images/DietPi_Pinebook-ARMv8-Buster.7z Direct download from dietpi.com]<br />
* Login with<br />
** Username: '''root'''<br />
** Password: '''dietpi'''<br />
<br />
<br />
<br />
== Slackware ==<br />
[[File:slackware.jpg|right|100px]]<br />
<br />
* Slackware is a very old, interesting, convenient and easy distribution.<br />
* Visit the project's website here (https://fail.pp.ua)<br />
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9439)<br />
* The Slackware build using LRZ compression algorithm, please visit the [https://github.com/ckolivas/lrzip lrunzip github site] for utility<br />
<br />
=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://3space.xyz/pineslarm/ Direct download from developer KRT site and look for slarm64-current-aarch64-base-rootfs-xxxxxxxx-x.x.xx-pinebook-build-xxxxxxxx.img.lrz]<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] ===<br />
* Only work on 1080P 11.6" Pinebook, not applicable to 14.1" and 11.6" Pinebook.<br />
* System with a graphical shell<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://3space.xyz/pineslarm/ Direct download from developer KRT site and look for slarm64-current-aarch64-xfce-rootfs-xxxxxxxx-x.x.xx-pinebook-build-xxxxxxxx.img.lrz]<br />
* Login with<br />
** Username : root<br />
** Password : password<br />
<br />
<br />
<br />
== Netrunner [No Longer Maintained] ==<br />
[[File:netrunner.jpg|right|100px]]<br />
<br />
=== Netrunner [20180417] [microSD Boot] ===<br />
* Only work on 14.1" and 11.6" Pinebook, not applicable to 1080P 11.6' Pinebook.<br />
* You can visit the Netrunner website [https://www.netrunner.com/netrunner-for-pinebook/ here]<br />
* DD image:<br />
** [https://sourceforge.net/projects/netrunneros/files/netrunner-arm/pinebook/ Direct download from sourceforge.net]<br />
<br />
<br />
<br />
== RISC_OS [No Longer Maintained] ==<br />
[[File:RISC_OS.png|right|100px]]<br />
<br />
=== RISC OS Community Build Image [microSD Boot] [19.02] ===<br />
* Only work on 14.1" and 11.6" Pinebook, not applicable to 1080P 11.6' Pinebook.<br />
* To learn more about RISC OS please visit [https://www.riscosopen.org/ RISC OS website] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https:///files.pine64.org/os/Pinebook/RISCOS/pine14_riscos_1GB.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4BE5698516FAF8420AEA34A422C20991<br />
*** size: 50MB<br />
<br />
<br />
<br />
= BSD Image Releases =<br />
<br />
==NetBSD==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD Community Build Image [microSD Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - Pinebook]<br />
** size: 345MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
<br />
<br />
==OpenBSD==<br />
[[File:Puffy_mascot_openbsd.png|right|100px]]<br />
<br />
=== OpenBSD 6.6-snapshot, Community Build Image (FVWM2 WM) ===<br />
* To learn more about OpenBSD please visit [https://www.openbsd.org OpenBSD main page]<br />
* DD image to microSD card or eMMC module (at least 8GB). Highly recommend using [https://etcher.io/ Etcher]<br />
** https://www.dropbox.com/s/79hpdpehrbbk984/pinebook-2019-11-04.img.tgz.sha256?dl=0 (sha256)<br />
** https://www.dropbox.com/s/yas1glfvvucb9a0/pinebook-2019-11-04.img.tgz?dl=0 (image)<br />
** compressed size: 3.6GB<br />
* Console and SSH default login:<br />
** username: pine64<br />
** username: pine64<br />
** root password: pine64<br />
* If you need more information please ping: https://forum.pine64.org/member.php?action=profile&uid=12423<br />
<br />
<br />
<br />
= Android Image Releases =<br />
<br />
== Android 7.x [No Longer Maintained] ==<br />
[[File:android_7.png|right|100px]]<br />
<br />
=== Android 7.1 Community Build Image [microSD Boot] by ayufan ===<br />
* Only work on 14.1" and 11.6" Pinebook, not applicable to 1080P 11.6' Pinebook.<br />
* Special thanks to ayufan, Icenowy, lennyraposo, longsleep, lukasz, tkaiser, Xalius and PINE64 community contributors<br />
* Please use good random IO access performance microSD card such as Samsung EVO when try out Android 7.1<br />
* DD image (advise 4GB microSD card and above):<br />
** [https://github.com/ayufan-pine64/android-7.1/releases/latest Direct download latest release build from ayufan github and look for android-7.1-pine-a64-pinebook-x.x.x-xx.img.gz]<br />
* Please allows some time (around 5 minutes) for the initialization process on 1st boot<br />
<br />
<br />
== Android 6.x eMMC ==<br />
[[File:android_6.png|right|100px]]<br />
<br />
=== Android 6.0.1 Stock Image for 14.1" and 11.6" Pinebook [microSD to eMMC] [20170605] ===<br />
* Rootable build, online update (OTA) only work when the build still not root<br />
* LCD resolution is 1366 x 768<br />
* Rooted DD image (advise 4GB microSD card and above):<br />
** [https://files.pine64.org/os/Pinebook/android/android-ver6.0.1-rooted-20170605-pinebook-sd2emmc-lpddr3.img.xz Direct download from pine64.org]<br />
*** MD5 (GZip file): C99BF459C6724BA73F12C532E87A8BA5<br />
*** File Size: 776MB<br />
<br />
<br />
=== Android 6.0.1 Stock Image for 1080P 11.6" Pinebook [microSD to eMMC] [20181001] ===<br />
* Rootable build<br />
* LCD resolution is 1920 x1080<br />
* Rooted DD image (advise 4GB microSD card and above):<br />
** [https://files.pine64.org/os/Pinebook/android/android-ver6.0.1-rooted-20181001-1080P-pinebook-sd2emmc-lpddr3.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): E433A148CEBD743EADE6CAA765331A4B<br />
*** File Size: 595MB<br />
<br />
=== Android 6.0.1 Stock Image for 1080P 11.6" Pinebook [microSD boot] [20181001] ===<br />
* Rootable build<br />
* LCD resolution is 1920 x1080<br />
* Please use high performance microSD card for Android boot which request frequent random read access. <br />
* Please ignore warning message regarding SD corrupted on home screen upper left corner<br />
* DD images:<br />
** For 8GB microSD Card<br />
*** [https://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-8GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): CD27DF6083E6A4A5E7C8B986EB92FAA7<br />
**** File Size: 553MB<br />
** For 16GB microSD Card<br />
*** [https://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-16GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 1376AAE8382E96FD7B45B0998A5CD6E9<br />
**** File Size: 703MB<br />
** For 32GB microSD Card<br />
*** [https://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-32GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): B54E7F323B316750654E385B078AEC58<br />
**** File Size: 867MB<br />
** For 64GB microSD Card<br />
*** [https://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-64GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): C8DBC6293EB51E58F91E27364C8C587D<br />
**** File Size: 734MB<br />
<br />
<br />
<br />
== /e/ [No Longer Maintained] ==<br />
[[File:e.png|right|100px]]<br />
<br />
=== /e/OS Community Build Image p [microSD and eMMC Boot] [20190926] ===<br />
* Only work on 1080P 11.6" Pinebook, not applicable to 14.1" and 11.6" Pinebook.<br />
* To learn more about /e/OS, please visit the [https://e.foundation/ official website]<br />
* Please check out [https://medium.com/@edevelopers.blog/e-os-ports-for-the-pinebook-and-pinephone-596139c76479 this article] on the Pinebook /e/ build.<br />
* For thread diiscussion please visit the [https://forum.pine64.org/showthread.php?tid=7954 PINE64 forum]<br />
* DD image (for 8GB microSD card and above)<br />
** [https://files.pine64.org/os/Pinebook/e/e-n-pinebook_20190926.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 4DC46A4E3ED2B47F4830E96DFCBBC6D8<br />
*** File Size: 685MB<br />
<br />
<br />
<br />
== Bliss OS [No Longer Maintained] ==<br />
[[File:bliss_os.png|right|100px]]<br />
<br />
=== Bliss OS [20170919] [microSD Boot] ===<br />
* Only work on 14.1" and 11.6" Pinebook, not applicable to 1080P 11.6" Pinebook.<br />
* An Open-Source OS, based on Android, for phones, tablets & PCs.<br />
* Multi-Windows Android Build<br />
* You can visit the Bliss OS website [https://blissroms.com/ here]<br />
* DD image:<br />
** [https://files.pine64.org/os/Pinebook/Bliss/Bliss-Pinebook_09.19.17_01.img.gz Direct download from pine64.org]<br />
*** MD5 (GZip file): 6B5BC28D69D575BA5448AD8081A0D356<br />
*** File Size: 943MB<br />
* Use the Taskbar launcher for Desktop mode UI<br />
<br />
<br />
<br />
= Linux BSP SDK =<br />
== Linux BSP [4.0] ==<br />
* [https://files.pine64.org/os/sdk/A64-ver4.0/A64-BSP-4.0.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 802D7C92D27177CBD17567359F9845A7<br />
** File Size: 4.67GB<br />
<br />
== Linux BSP [3.0] ==<br />
* [https://files.pine64.org/os/sdk/A64-ver3.0/A64-BSP-3.0.tgz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 898ACF446851DF3BE7B643F62CE3CE84<br />
** File Size: 4.18GB<br />
<br />
== Linux BSP [2.0], kernel [v3.10], with GPL compliance header ==<br />
* [https://files.pine64.org/os/sdk/A64-ver2.0/A64-BSP-2.0-GPL.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 2EE11C9AED246C17995493F213A6A6DA<br />
** File Size: 6.41GB<br />
<br />
= Android SDK =<br />
== Android Oreo [v8.1] ==<br />
* [https://files.pine64.org/os/sdk/A64-ver4.0/A64-Android-8.1-SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-Gzip file): 7E73672FE84F8CD099264D640E107EA3<br />
** File Size: 28.87.95GB<br />
<br />
== Android Nougat [v7.0] ==<br />
* [https://files.pine64.org/os/sdk/A64-ver3.0/A64-Android-7.0-SDK.tgz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 5D23D65BC1AA32B9048F62A4176BD9B3<br />
** File Size: 22.60GB<br />
<br />
== Android Marshmallow [v6.0] ==<br />
* [https://files.pine64.org/os/sdk/A64-ver2.0/A64-Android-6.0-SDK.zip Direct Download from pine64.org]<br />
** MD5 (Zip file): 12362D0B63EBF29FC363A50A942346D5<br />
** File Size: 12.17GB<br />
<br />
= Mali-400 64-bit Driver =<br />
== Mali-400 64-bit Driver [20160622] ==<br />
* [[Mali_Driver|Mali 64-bit Driver Download]]<br />
<br />
= Other Tools =<br />
* [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing Allwinner PhoenixCard Bootable SD-Card Creator]<br />
* [https://chinagadgetsreviews.com/download-dragonface-latest-version-v-2-2-5.html Allwinner DragonFace V2.2.5 software that will let you edit and modify A64 Android Build PhoenixCard image]<br />
** [https://mega.nz/#!QxEjmaKB!S5nsVnzXVZg5aJ6qLtPOx1yJDPlbl0Vs4iV9VliRpE8 Direct download at Mega]<br />
<br />
= Checking microSD Card Performance and whether it is Counterfeit =<br />
* [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]<br />
* [https://oss.digirati.com.br/f3/ F3 - an alternative to h2testw]<br />
This will help you to determine if the SD-Card is Counterfeit Drive or not<br />
<br />
[[Category:PineBook]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=PINE_H64&diff=10698PINE H642021-06-12T21:43:09Z<p>JerseyDevil: micoSD to microSD (x8)</p>
<hr />
<div>The '''PINE H64''' is a Single Board Computer by Pine64. It is powered by an Allwinner “H6” Quad-Core ARM Cortex A53 64-Bit Processor with a MALI T-722 GPU. The PINE H64 is equipped with up to 3GB of LPDDR3 PC-1600 system memory and 128Mbit of SPI boot Flash. There is also an optional eMMC module (up to 128GB) and a microSD slot for booting. The board is equipped with an onboard 802.11n Wifi/BT chipset, one USB 3.0 host port, two USB 2.0 host ports, Gigabit Ethernet, a PI-2 GPIO bus, an Euler GPIO bus as well as many other peripheral device interfaces such as UART, SPI, and I<sup>2</sup>C.<br />
<br />
== PINE H64 Model ==<br />
<br />
There are two types of PINE H64 models:<br />
<br />
Click on the model A photo to access the model A main page. <br />
<br />
For model B, stay on the current page.<br />
<br />
* [[PINE H64 Model-A Main Page]]<br />
<br />
<br />
== PINE H64 Model B Software and OS Image Downloads ==<br />
<br />
= Linux Image Releases =<br />
<br />
== Armbian==<br />
[[File:armbian.png|right|100px]]<br />
<br />
=== Armbian Debian Buster for XFCE Desktop Usage ===<br />
* Armbian provides a mainline kernel build images for Debian Buster<br />
* DD image (for 8GB microSD card or eMMC module and above)<br />
** [https://dl.armbian.com/pineh64/Buster_current_desktop Armbian's PINE H64 Debian Buster download site]<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pine-h64/ site]<br />
<br />
=== Armbian Debian Buster for Server and Light Desktop Usage ===<br />
* Armbian provides a mainline kernel build images for Debian Buster<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
** [https://dl.armbian.com/pineh64/Buster_current Armbian's PINE H64 Debian Buster download site]<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pine-h64/ site]<br />
<br />
=== Armbian Ubuntu Bionic for Server and Light Desktop Usage ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Bionic<br />
* DD image (for 8GB microSD card or eMMC module and above)<br />
** [https://dl.armbian.com/pineh64/Bionic_current Armbian's PINE H64 Ubuntu Bionic download site]<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pine-h64/ site]<br />
<br />
=== Armbian Ubuntu Focal for Server and Light Desktop Usage ===<br />
* Armbian provides a mainline kernel build images for Ubuntu Focal<br />
* DD image (for 8GB microSD card or eMMC module and above)<br />
** [https://dl.armbian.com/pineh64/Focal_current Armbian's PINE H64 Ubuntu Focal download site]<br />
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pine64/ site]<br />
<br />
<br />
<br />
== AOSC ==<br />
[[File:aosc.png|right|100px]]<br />
<br />
=== AOSC Community Build Image with Mate Desktop [microSD Boot] [20190708] ===<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
* Known issue: no audio sound output.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-07-08.img.xz Direct download from pine64.org]<br />
*** MD5 (GZip file): 7A6EC6A088BA75E4F4BEF884EA93EE6C<br />
*** File Size: 3.47GB<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
<br />
=== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180709] ===<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
* Known issue: no audio sound output.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-07-09_mmc2.img.xz Direct download from pine64.org]<br />
*** MD5 (GZip file): FFEA20480A305A644D2C4CB52DC43046<br />
*** File Size: 3.49GB<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
<br />
=== AOSC Community Build Image with Mate Desktop [microSD Boot] [20190218] ===<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
* Known issue: no audio sound output.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-02-18.img.xz Direct download from pine64.org]<br />
*** MD5 (GZip file): 0274E1011BA58A45CB2B2104CEBD23AA<br />
*** File Size: 2.63GB<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
<br />
=== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180216] ===<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
* Known issue: no audio sound output.<br />
* DD image (for 8GB microSD card and above)<br />
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-02-16_mmc2.img.xz Direct download from pine64.org]<br />
*** MD5 (GZip file): 34F3F6813EF00FAF49B1C2A1562EE39D<br />
*** File Size: 2.63GB<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
<br />
<br />
<br />
== Manjaro ARM ==<br />
[[File:Manjaro.png|right|100px]]<br />
<br />
* Installing and using from Manjaro x64 repositories:<br />
::In your Desktop Environment use the Package Manager and search for '''manjaro-arm-tools''' and install.<br />
::Or in the Terminal use '''sudo pacman -S manjaro-arm-tools''' to install the package.<br />
::Then in the Terminal use '''sudo buildarmimg -d pine-h64 -e <your-favourite-de>''', but change <your favorite DE> to one from the list of supported DE's:<br />
:::* minimal<br />
:::* lxqt<br />
:::* kde-plasma<br />
:::* mate<br />
:::* xfce<br />
:::* i3<br />
:::* sway<br />
:::* gnome (experimental)<br />
:::* plasma-mobile (experimental)<br />
:::* phosh (experimental)<br />
:::* cubocore (not complete yet)<br />
:::* server (not complete yet, unmaintained)<br />
* To find out more about Manjaro-Arm-Tools and available options please visit their [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools site]<br />
<br />
<br />
<br />
== DietPi ==<br />
[[File:dietpi.png|right|100px]]<br />
<br />
* DietPi is a '''lightweight''', yet '''easy to setup''' and '''feature-rich''' Linux distribution, based on '''Debian'''.<br />
* To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation].<br />
* Discuss the PINE H64 build on the [https://forum.pine64.org/showthread.php?tid=12531 PINE64 forum thread].<br />
* DD image (for 4 GiB micro SD card and above)<br />
** [https://dietpi.com/downloads/images/DietPi_PINEH64-ARMv8-Buster.7z Direct download from dietpi.com]<br />
* Login with<br />
** Username: '''root'''<br />
** Password: '''dietpi'''<br />
<br />
<br />
<br />
== LibreELEC (KODI) ==<br />
[[File:libreelec.jpg|right|100px]]<br />
<br />
=== Nightly Build Image [microSD and eMMC Boot] ===<br />
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://test.libreelec.tv/ Pine A64+ build direct download from Libreelec nightly build site and look for LibreELEC-H6.arm-9.80-nightly-xxxxxxxx-xxxxxxx-pine-h64-model-b.img.gz]<br />
** FEATURES:<br />
*** mainline kernel & U-Boot<br />
*** latest Kodi<br />
*** HDMI CEC<br />
*** multi channel HDMI audio (correct audio output must be selected)<br />
*** IR receiver<br />
<br />
<br />
<br />
= BSD Image Releases =<br />
<br />
== NetBSD ==<br />
[[File:netbsd.png|right|100px]]<br />
<br />
=== NetBSD Community Build Image [microSD Boot] ===<br />
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page] <br />
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]<br />
** [https://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select PINE H64]<br />
** size: 345MB<br />
* Console and SSH default login:<br />
** username: root<br />
** password: [none]<br />
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]<br />
<br />
<br />
<br />
= Android Image Releases =<br />
<br />
== Android 9.0 ==<br />
[[File:android_9.png|right|100px]]<br />
<br />
=== Stock Android 9.0 microSD Card to eMMC 20190523] ===<br />
* DD image to microSD card, install eMMC module, plug in microSD card into slot and boot.<br />
** After power ON the box for 2-3 second, it will start writing the new image to the eMMC with progress bar. Once finished upload to eMMC, take out microSD card and reboot.<br />
* Highly recommend using [https://etcher.io/ Etcher]<br />
* Support 4K HDR playeback<br />
* non rooted version<br />
* PINE64 IR mapping not yet implemented<br />
* Please allow 10-15 minutes boot up time on first time for initialization<br />
* DD images:<br />
** Using 8GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-sd2emmc.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 3B18BA6C82BF3E0020D0B54E9520755E<br />
**** File Size: 1.21GB<br />
<br />
=== Stock Android 9.0 microSD and eMMC Boot 20190523] ===<br />
* Support 4K HDR playeback<br />
* Highly recommend using [https://etcher.io/ Etcher]<br />
* non rooted version<br />
* PINE64 IR mapping not yet implemented<br />
* Please allow 20-25 minutes boot up time on first time for initialization<br />
* DD images:<br />
** For 8GB microSD Card or eMMC module<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-8GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): D2244B9FDD5100A4687C16C4A8034884<br />
**** File Size: 1.05GB<br />
** Using 16GB microSD Card or eMMC module<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-16GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 9AC957ED7B71BA37A363098F6F15C32C<br />
**** File Size: 1.30GB<br />
** Using 32GB microSD Card oe eMMC module<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-32GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 18BE1EDA248EDDAF35B80195954097A8<br />
**** File Size: 1.28GB<br />
** Using 64GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-64GB.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 49EEEBFDEC0337A47879EBE9439F4937<br />
**** File Size: 1.02GB<br />
<br />
=== Stock Android 9.0 Phoenix Card image 20190523] ===<br />
* Only use Phoenixcard method as last resort option<br />
*** [https://files.pine64.org/os/pine-h64/android/PhoenixCard4_1_3.zip Phoenixcard ver 4.1.3 utility direct download from pine64.org]<br />
* Select "Start up" as option for SD Card boot<br />
* Select "Product" as option for "SD Card to eMMC" method<br />
* non rooted version<br />
* PINE64 IR mapping not yet implemented<br />
* Please allow 10-15 minutes boot up time on first time for initialization<br />
* This process may not everytime build up successfully<br />
** Using 4GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_20190523_stock_android_9.0-PhoenixCard.img.gz Direct download from pine64.org]<br />
**** MD5 (Gzip file): B0202A03C189897DEAFCC178B5829BEF<br />
**** File Size: 389MB<br />
<br />
<br />
<br />
== Android 7.x ==<br />
[[File:android_7.png|right|100px]]<br />
<br />
=== Stock Android 7.0 microSD Card Boot 20190115] ===<br />
* Support 4K HDR playeback<br />
* Highly recommend using [https://etcher.io/ Etcher]<br />
* Please allow 10-15 minutes boot up time on first time for initialization<br />
* DD images:<br />
** For 8GB microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-8G.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 12110D73CA7ADE749C948D63499B2AE3<br />
**** File Size: 417MB<br />
** Using 16GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-16G.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): FE6DB577CE6D54D3DDF25FD6CB9A8839<br />
**** File Size: 426MB<br />
** Using 32GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-32G.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 8E37374D87FFDB5BC6D08635A168A152<br />
**** File Size: 444MB<br />
** Using 64GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-64G.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): BA29EBCE85A71C408F6AB9FD3EA23885<br />
**** File Size: 482MB<br />
<br />
<br />
=== Stock Android 7.0 microSD Card to eMMC 20190115] ===<br />
* DD image to microSD card, install eMMC module, plug in muicroSD vard into slot and boot. <br />
** After power ON the box for 2-3 second, it will start writing the new image to the eMMC with progress bar. Once finished upload to eMMC, take out microSD card and reboot.<br />
* Highly recommend using [https://etcher.io/ Etcher]<br />
* Support 4K HDR playeback<br />
* Please allow 10-15 minutes boot up time on first time for initialization<br />
* DD images:<br />
** Using 4GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sd2emmc.img.gz Direct download from pine64.org]<br />
**** MD5 (GZip file): 61133A2967BDD2806F6AD2E144DD06AB<br />
**** File Size: 414MB<br />
<br />
<br />
<br />
=== Stock Android 7.0 Phoenix Card image 20190115] ===<br />
* Only use Phoenixcard method as last resort option<br />
*** [https://files.pine64.org/os/pine-h64/android/PhoenixCard4_1_3.zip Phoenixcard ver 4.1.3 utility direct download from pine64.org]<br />
* Select "Start up" as option for SD Card boot<br />
* Select "Product" as option for "SD Card to eMMC" method<br />
* Please allow 10-15 minutes boot up time on first time for initialization<br />
* This process may not everytime build up successfully<br />
** Using 4GB or above microSD Card<br />
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-phoenixcard.img Direct download from pine64.org]<br />
**** MD5 (IMG file): 679E5F1A0F772B9F750E4139C8B025F0<br />
**** File Size: 822MB<br />
<br />
<br />
== SoC and Memory Specification ==<br />
* Based on Allwinner H6<br />
[[File:Allwinner_H64.png]]<br />
<br />
=== CPU Architecture ===<br />
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1488Mhz]<br />
* A power-efficient ARM v8 architecture<br />
* 64 and 32bit execution states for scalable high performance<br />
* Trustzone technology supported<br />
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function<br />
* Support Large Physical Address Extensions(LPAE)<br />
* VFPv4 Floating Point Unit<br />
* 32KB L1 Instruction cache and 32KB L1 Data cache<br />
* 512KB L2 cache<br />
<br />
=== GPU Architecture ===<br />
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t720-gpu ARM Mali T-720MP2 Dual-core GPU]<br />
* Supports OpenGL ES 3.1/3.0/2.0/1.1, OpenCL 1.2/1.1<br />
* Supports ATSC (Adaptive Scalable Texture Compression)<br />
* Supports FAST(4x)FSAA, IO Coherency <br />
* Floating point operation greater than 70 GFLOPS<br />
<br />
=== System Memory ===<br />
* RAM Memory Variants: 1GB, 2GB, and 3GB LPDDR3.<br />
* Storage Memory: PINE H64 boards have built-in 128Mb SPI Flash memory, use '''bootable eMMC module''', '''bootable microSD Cards''' or USB attached storage.<br />
<br />
<br />
<br />
== Board Features ==<br />
<br />
=== Video ===<br />
* Digital Video 4KP60 (Type A - full)<br />
<br />
=== Audio ===<br />
* 3.5mm stereo earphone/microphone plug<br />
<br />
=== Network ===<br />
* 10/100/1000Mbps Ethernet<br />
* WiFi 802.11 b/g/n/ac with Bluetooth 4.0/4.1<br />
<br />
=== Storage ===<br />
* microSD - bootable, support SDHC and SDXC, storage up to 256GB<br />
* USB - 1 USB3.0 Host port and 2 USB2.0 Host port<br />
<br />
=== Expansion Ports ===<br />
* RTC - Real Time Clock Battery Connector<br />
* Wifi/BT Module Header - SDIO 3.0 and UART<br />
* 2x20 pins "Pi2" GPIO Header<br />
<br />
<br />
== Pine H64 Model B Board Information, Schematics and Certifications ==<br />
* Board Dimensions: 85mm x 56mm x 18.8mm<br />
* Input Power: DC 5V @ 3A, 3.5mm OD/ 1.35mm ID DC jack connector<br />
<br />
* [https://files.pine64.org/doc/Pine%20H64/Pine%20H64%20model%20B%20Port%20Assignment%20rev2.0.pdf PINE H64 Model B Pi-2 Bus Connector Pin Assignment]<br />
<br />
* PINE H64 Board Schematic:<br />
** [https://files.pine64.org/doc/Pine%20H64/PINE-H6-model-B-20181212-schematic.pdf PINE H64 Model B 1GB/2GB/3GB Rev 1.2 Board Schematic]<br />
<br />
* PINE H64 Model B Certification:<br />
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submits the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.<br />
** [https://files.pine64.org/doc/cert/PINE-H64B%20FCC%20S19041102001001%20Certificate.pdf PINE-H64 Model-B FCC Certificate]<br />
** [https://files.pine64.org/doc/cert/PINE-H64B%20CE-EMC%20S19041102001001%20Certificate.pdf PINE-H64 Model-B CE Certificate]]<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Allwinner H6 SoC information:<br />
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner-H6-Brief_V1.0.pdf Allwinner H6 SoC Brief Introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner_H6%20V200_Datasheet_V1.1.pdf Allwinner H6 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner_H6%20V200_User_Manual_V1.1.pdf Allwinner H6 SoC User Manual V1.0 (Official Release Version)]<br />
* X-Powers AXP805 PMU (Power Management Unit) information:<br />
** [https://files.pine64.org/doc/datasheet/pine-h64/AXP805_Datasheet_V1.0_en.pdf X-Powers AXP805 Data Sheet V1.0 (Official Release Version)]<br />
* LPDDR3 (178 Balls) SDRAM:<br />
** [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]<br />
** [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]<br />
** [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]<br />
* Ethernet PHY information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE H64 Board]<br />
* Wifi/BT module information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
* Remote control button mapping<br />
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE H64 Button Mapping]<br />
<br />
<br />
= Mali-T720 driver =<br />
<br />
Here is a good DRM powerpoint presentation by Free Electron: https://free-electrons.com/pub/conferences/2017/kr/ripard-drm/ripard-drm.pdf<br />
<br />
Here is the DRM video presentation by Free Electron: https://www.youtube.com/watch?v=LbDOCJcDRoo<br />
<br />
== 32-bit Wayland MALI Driver: ==<br />
** [https://files.pine64.org/doc/MALI/MALI%20EULA.pdf MALI EULA document]<br />
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-016-linux-opengles-release-wayland-server-gbm-composer-arm32-glibc.tar.bz2 MALI-T720 32-bit server binary driver and binary download]<br />
*** MD5: F2186A4CAE505A76E0758735886FE682<br />
*** File Size: 3.4MB<br />
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-016-linux-opengles-release-wayland-client-gbm-composer-arm32-glibc.tar.bz2 MALI-T720 32-bit client binary driver and binary download]<br />
*** MD5: F316A78AFABE87E69C8F816D18F15D68<br />
*** File Size: 3.4MB<br />
<br />
== 64-bit Wayland MALI Driver: ==<br />
** [https://files.pine64.org/doc/MALI/MALI%20EULA.pdf MALI EULA document]<br />
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-018-linux-opengles-release-wayland-server-gbm-composer-arm64-glibc.tar.bz2 MALI-T720 64-bit server binary driver and binary download]<br />
*** MD5: 13CC8DCB7CF068D80DFC16281E95E9D7<br />
*** File Size: 5.0MB<br />
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-018-linux-opengles-release-wayland-client-gbm-composer-arm64-glibc.tar.bz2 MALI-T720 64-bit client binary driver and binary download]<br />
*** MD5: 951BAD6ED66D4CB904CFE0D65F2855E8<br />
*** File Size: 5.0MB<br />
<br />
= Linux BSP SDK =<br />
<br />
== Linux BSP Kernel 4.9 ==<br />
* [https://files.pine64.org/SDK/PINE-H64/PINE%20H64B%20BSP%204.9%20lichee.tar.xz Direct Download from pine64.org]<br />
** MD5 (TAR-XZ file): 06B675B1C217D4CC6A21FF320DA250C1<br />
** File Size: 5.04GB<br />
<br />
= Android SDK =<br />
<br />
== Android Pie 9.0 SDK version 1.0 ==<br />
* [https://files.pine64.org/SDK/PINE-H64/PINE%20H64B%20android%209.0.tar.xz Direct Download from pine64.org]<br />
** MD5 (TAR-XZ file): 734B4DBB03CAF82A4E955F7E83DE0C65<br />
** File Size: 29.14GB<br />
<br />
== Other Resources ==<br />
<br />
[[Category:Pine H64]] [[Category:Allwinner H6]]</div>JerseyDevilhttps://wiki.pine64.org/index.php?title=SOEDGE_Software_Releases&diff=10697SOEDGE Software Releases2021-06-12T21:41:47Z<p>JerseyDevil: micoSD to microSD (x1)</p>
<hr />
<div>= Linux Image Releases =<br />
== BSP ==<br />
=== Full BSP Linux image ver 1.1 ===<br />
<br />
* This is full image version can be apply to model A baseboard<br />
* DD image (for 8GB microSD card or eMMC Module and above)<br />
* [https://files.pine64.org//os/SOEdge/stock/SOEdge_linux_v1.1.img.gz Direct Download from pine64.org]<br />
** MD5 (GZip file): 636ebeb66d6d0fc0929397d541b0ce83<br />
** File Size: 119MB<br />
<br />
=== Neural AI Stick Linux image ver 1.1 ===<br />
<br />
* This is USB 3.0 Neural AI Stick image version<br />
* DD image (for 8GB eMMC Module and above)<br />
* [https://files.pine64.org//os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz Direct Download from pine64.org]<br />
** MD5 (GZip file): 6fddf73a34ea2a1cb6f36be673567b5f<br />
** File Size: 47MB<br />
<br />
= Linux BSP SDK =<br />
<br />
== Full BSP SDK ver 1.1 ==<br />
<br />
* [https://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_SDK_v1.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): a66c92e52824762d7c0a63400d6342ea<br />
** File Size: 13.55GB<br />
<br />
== Neural AI Stick BSP SDK ver 1.1 ==<br />
<br />
* [https://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_USB_Dongle_SDK_v1.1.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 46f12441e8c35c06184681f355c89651<br />
** File Size: 9.65GB<br />
<br />
[[Category:SOPine]]</div>JerseyDevil