https://wiki.pine64.org/api.php?action=feedcontributions&user=UniversalSuperBox&feedformat=atomPINE64 - User contributions [en]2024-03-19T11:03:25ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=PineNote&diff=11109PineNote2021-08-20T03:55:29Z<p>UniversalSuperBox: </p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Built in stereo speakers<br />
* 4 x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
The following topics have resolved:<br />
<br />
* [[PineNote/Hardware_Changes/Closed_Case_UART]]<br />
* '''Could the USB-C port support USB 3.1 5Gbps?''' Yes and no. The RK3566 only has a host-mode 5Gbps controller, meaning it can only negotiate such a high data rate with a device such as a flash drive. When the RK3566 is acting as a device, it only supports 480Mbps transfer rates. The hardware required to switch between these modes would raise the PineNote's price unreasonably. Therefore, the USB-C port will remain at USB 2.0 speeds for Host and Device mode.<br />
* '''Could the USB-C port output DisplayPort?''' Yes and no. The hardware required to support such a feature would raise the PineNote's price unreasonably. Therefore, DisplayPort output will not be possible through the USB-C port.<br />
* '''Where is the microSD card slot?''' The case design of the PineNote is fixed, making physical changes like adding a microSD card slot would raise the cost unreasonably. However, revisions of the PineNote motherboard after 1.1 will feature an internal ribbon cable connector where a microSD card slot may be attached. Attaching such a device will require taking the PineNote apart.<br />
* '''How will I install software to the PineNote?''' This is a hardware and software question. If the software on your PineNote is completely broken and cannot boot to a recoverable state, a Hall (magnet) sensor was fitted to the PineTab motherboard as U9009. This sensor is attached to SARADC_VIN0_KEY/RECOVERY on the RK3566. With the device powered off, holding a magnet over U9009 and plugging in a USB-C cable causes the device to boot into [http://opensource.rock-chips.com/wiki_Rockusb|"rockusb"] flash mode. With proper flashing software and drivers, it should be possible to load a new operating system using rockusb if the system is soft-bricked. Of course, software vendors will need to be more careful with flashing firmware and providing useful "recovery" options on this device due to this process's relative difficulty to other PINE64 devices.<br />
<br />
==== Unresolved ====<br />
<br />
The following concerns have been brought up as open, unanswered topics:<br />
<br />
* Does [https://en.wikipedia.org/wiki/USB-C#Audio_Adapter_Accessory_Mode_2|USB-C Audio Adapter Accessory Mode] work? It appears that the Headphone output of the audio codec was routed to the USB-C audio+USB switch, but it's unclear whether CC lines are hooked up correctly for detection of such a device. The PineNote hardware team will be testing this functionality soon (as of August 19, 2021).<br />
* Why is the Headphone output of the audio codec routed to the speakers? HPL_OUT is routed from the RK817 PMIC and audio codec to U9010 (the USB-C switch) and U6 (the audio amplifier). SPK_OUT is unused. It seems like SPK_OUT should be routed to U6 and HPL_OUT to U9010.<br />
* Nitpick: The cold white charging LED bleeds through the gap between the rear case and the device's face. It does not bleed onto the screen, but it is jarring in low-light conditions or when the screen is amber. Could be resolved in software by turning off the charge LED when the screen is on.<br />
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
== Hardware troubleshooting guide ==<br />
At present, nothing is available.<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11108PineNote2021-08-20T03:54:11Z<p>UniversalSuperBox: </p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Built in stereo speakers<br />
* 4 x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
The following topics have resolved:<br />
<br />
* [[PineNote/Hardware_Changes/Closed_Case_UART]]<br />
* '''Could the USB-C port support USB 3.1 5Gbps?''' Yes and no. The RK3566 only has a host-mode 5Gbps controller, meaning it can only negotiate such a high data rate with a device such as a flash drive. When the RK3566 is acting as a device, it only supports 480Mbps transfer rates. The hardware required to switch between these modes would raise the PineNote's price unreasonably. Therefore, the USB-C port will remain at USB 2.0 speeds for Host and Device mode.<br />
* '''Could the USB-C port output DisplayPort?''' Yes and no. The hardware required to support such a feature would raise the PineNote's price unreasonably. Therefore, DisplayPort output will not be possible through the USB-C port.<br />
* '''Where is the microSD card slot?''' The case design of the PineNote is fixed, making physical changes like adding a microSD card slot would raise the cost unreasonably. However, revisions of the PineNote motherboard after 1.1 will feature an internal ribbon cable connector where a microSD card slot may be attached. Attaching such a device will require taking the PineNote apart.<br />
* '''How will I install software to the PineNote?''' This is a hardware and software question. If the software on your PineNote is completely broken and cannot boot to a recoverable state, a Hall (magnet) sensor was fitted to the PineTab motherboard as U9009. This sensor is attached to SARADC_VIN0_KEY/RECOVERY on the RK3566. With the device powered off, holding a magnet over U9009 and plugging in a USB-C cable causes the device to boot into [http://opensource.rock-chips.com/wiki_Rockusb|"rockusb"] flash mode. With proper flashing software and drivers, it should be possible to load a new operating system using rockusb if the system is soft-bricked. Of course, software vendors will need to be more careful with flashing firmware and providing useful "recovery" options on this device due to this process's relative difficulty to other PINE64 devices.<br />
<br />
The following concerns have been brought up as open, unanswered topics:<br />
<br />
* Does [https://en.wikipedia.org/wiki/USB-C#Audio_Adapter_Accessory_Mode_2|USB-C Audio Adapter Accessory Mode] work? It appears that the Headphone output of the audio codec was routed to the USB-C audio+USB switch, but it's unclear whether CC lines are hooked up correctly for detection of such a device. The PineNote hardware team will be testing this functionality soon (as of August 19, 2021).<br />
* Why is the Headphone output of the audio codec routed to the speakers? HPL_OUT is routed from the RK817 PMIC and audio codec to U9010 (the USB-C switch) and U6 (the audio amplifier). SPK_OUT is unused. It seems like SPK_OUT should be routed to U6 and HPL_OUT to U9010.<br />
* Nitpick: The cold white charging LED bleeds through the gap between the rear case and the device's face. It does not bleed onto the screen, but it is jarring in low-light conditions or when the screen is amber. Could be resolved in software by turning off the charge LED when the screen is on.<br />
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
== Hardware troubleshooting guide ==<br />
At present, nothing is available.<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote/Hardware_Changes/Closed_Case_UART/2021-08-15&diff=11106PineNote/Hardware Changes/Closed Case UART/2021-08-152021-08-20T02:04:03Z<p>UniversalSuperBox: Created page with "For some relevant takeaways from this discussion, see PineNote/Hardware Changes/Closed Case UART#August 15, 2021 Times are in UTC-5 Logs collected from #pinedev on irc.p..."</p>
<hr />
<div>For some relevant takeaways from this discussion, see [[PineNote/Hardware Changes/Closed Case UART#August 15, 2021]]<br />
<br />
Times are in UTC-5<br />
<br />
Logs collected from #pinedev on irc.pine64.org<br />
<br />
<br />
'''Sunday, August 15, 2021'''<br />
<br />
7:42:56 PM <@UniversalSuperBox> Anyone know of an existing standard to route 115200 baud serial over USB-C?<br />
<br />
7:43:18 PM <megi> looks like mostly binary garbage, rather than assembly<br />
<br />
7:44:09 PM <dsimic> UniversalSuperBox: I don't<br />
<br />
7:44:18 PM <@MartijnBraam> putting the uart on one of the usb-c pairs? :D<br />
<br />
7:44:29 PM <@MartijnBraam> or the google pixel standard<br />
<br />
7:44:47 PM <@konradybcio> or a separate usb for uart, honeycomb style :D<br />
<br />
7:45:08 PM <dsimic> or a magnetic switch :)<br />
<br />
7:46:03 PM <megi> or a glass mercury switch<br />
<br />
7:46:09 PM <@UniversalSuperBox> Modifying the case is not an option.<br />
<br />
7:46:34 PM <@MartijnBraam> your hacking it into a product?<br />
<br />
7:46:37 PM <dsimic> there's some "Debug Accessory Mode" for Type-C<br />
<br />
7:46:41 PM <@UniversalSuperBox> No, the PineNote.<br />
<br />
7:47:09 PM <@MartijnBraam> https://wiki.postmarketos.org/wiki/Serial_debugging:Cable_schematics<br />
<br />
7:47:35 PM <dsimic> https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode<br />
<br />
7:48:01 PM <dsimic> "In this mode, all digital circuits are disconnected from the connector, and the 14 bold pins can be used to expose debug related signals (e.g. JTAG interface)."<br />
<br />
7:48:17 PM <dsimic> so, it should be possible to route the serial port<br />
<br />
7:48:19 PM <@MartijnBraam> that's probably the best mode<br />
<br />
7:48:46 PM <dsimic> or even to route microSD lines :)<br />
<br />
7:48:56 PM <dsimic> or both! :)<br />
<br />
7:49:08 PM <dsimic> woo-hoo! :)<br />
<br />
7:49:19 PM <@MartijnBraam> jumpdrive for pinenote :P<br />
<br />
7:49:28 PM <@UniversalSuperBox> microSD was my thought too.<br />
<br />
7:49:47 PM <dsimic> problem solved... maybe :)<br />
<br />
7:50:00 PM <@UniversalSuperBox> There is almost definitely a confounding factor that we don't see yet.<br />
<br />
7:50:17 PM <@UniversalSuperBox> I've been trying to lower expectations all afternoon, so I'm a bit burnt.<br />
<br />
7:51:10 PM <dsimic> there surely needs to be some logic on the host side that allows the "DAM" to work<br />
<br />
7:51:13 PM <@UniversalSuperBox> Probably requires a USB-C controller on the motherboard or something.<br />
<br />
7:51:26 PM <@MartijnBraam> probably<br />
<br />
7:51:29 PM <@UniversalSuperBox> And the anx is basically not an option except for the PinePhone, they can't be bought.<br />
<br />
7:52:03 PM <@MartijnBraam> can't the rk3599 detect the debug attachment condition and toggle a gpio to control a simple mux?<br />
<br />
7:52:23 PM <@UniversalSuperBox> Doesn't help for debugging a bootloader, does it?<br />
<br />
7:52:33 PM <@MartijnBraam> hmm true<br />
<br />
7:53:03 PM <@MartijnBraam> the resistors on the connector could be measured with a MCU hooked into it :P<br />
<br />
8:13:52 PM <dsimic> with some additional logic, this IC might do the trick: https://www.ti.com/lit/ds/symlink/hd3ss3212.pdf<br />
<br />
8:15:58 PM <@UniversalSuperBox> Finding an existing device with such a function would be more useful than finding the building blocks to create it ourselves.<br />
<br />
8:16:06 PM <@UniversalSuperBox> Great artists copy, as it were.<br />
<br />
8:16:34 PM <dsimic> I agree, but I haven't been able to find such device yet<br />
<br />
8:17:31 PM <@UniversalSuperBox> I'm not sure if SuzyQable is such a use or not<br />
<br />
8:22:43 PM <@UniversalSuperBox> Reading the spec, I'm becoming less and less hopeful that the closed-case debugging feature can be enabled through mostly passive components.<br />
<br />
8:23:19 PM <@UniversalSuperBox> <br />
<br />
8:31:29 PM <dsimic> if all that fails, having an internal microSD card slot and both Linux and Windows applications that can use maskrom mode to flash OS images is still an acceptable solution, IMHO<br />
<br />
8:37:33 PM <@UniversalSuperBox> Yes, the SuzyQable is DAM, assuming the offhand comment at https://chromium.googlesource.com/chromiumos/platform/ec/+/HEAD/docs/usb-c.md is true<br />
<br />
8:37:41 PM <@UniversalSuperBox> > Debug accessory mode, e.g. Case Closed Debugging (CCD)<br />
<br />
8:41:45 PM <dsimic> the PineNote already uses this IC for CC control: https://cdn.datasheetspdf.com/pdf-down/W/U/S/WUSB3801-WillSEMI.pdf<br />
<br />
8:42:17 PM <dsimic> which means that it could be replaced with a similar IC that does that and has additional capability to detect DAM<br />
<br />
8:42:28 PM <dsimic> TI seems to have such ICs<br />
<br />
8:42:46 PM <dsimic> (I know, building blocks again, but do we have anything better?)<br />
<br />
8:43:48 PM <@smaeul> dsimic: that chip already has the ability to detect DAM<br />
<br />
8:43:59 PM <@smaeul> the WUSB3801<br />
<br />
8:44:04 PM <dsimic> I was going to write exactly that :)<br />
<br />
8:44:12 PM <dsimic> page 13 in the datasheet<br />
<br />
8:46:33 PM <@UniversalSuperBox> Many hands make light work โ thanks so much for looking at it folks<br />
<br />
8:46:50 PM <dsimic> hm, but it can't drive an output high/low, which means that a driver would need to select the switch position<br />
<br />
8:46:58 PM <dsimic> not an option while booting<br />
<br />
8:47:31 PM <dsimic> some TI ICs can drive a DEBUG output upon detecting DAM<br />
<br />
8:47:49 PM <dsimic> that DEBUG output can go to HD3SS3212<br />
<br />
8:49:07 PM <dsimic> https://datasheet.lcsc.com/szlcsc/2002291210_Texas-Instruments-Texas-Instruments-TPS25810RVCR_C473913.pdf<br />
<br />
8:49:08 PM <@smaeul> HD3SS3212 is way overkill. that's for SuperSpeed lines<br />
<br />
8:49:33 PM <dsimic> I'm not saying that it must be HD3SS3212, I'm just giving possible examples<br />
<br />
8:50:02 PM <@UniversalSuperBox> Small note that the current parts were selected for availability as much as they were for ergonomics.<br />
<br />
8:50:25 PM <@tl_lim> just looking for a way that bring up console UART thru USB-C port so that developer no need to open up the PineNote back cover<br />
<br />
8:50:34 PM <dsimic> if we agree upon a solution, finding actually available parts is the next step :)<br />
<br />
8:51:02 PM <@tl_lim> Lets not goes wild.<br />
<br />
8:51:06 PM <@UniversalSuperBox> UART is the only thing we feel we really need, microSD is a bonus. We've only got a week to make schematic changes, and big changes are still a bad idea.<br />
<br />
8:51:44 PM <@UniversalSuperBox> It'd be lame, but could we bring 3.3v uart out over SB1 and SB2?<br />
<br />
8:52:13 PM <@UniversalSuperBox> Or would USB-IF scream?<br />
<br />
8:52:32 PM <@MartijnBraam> just add another magnet :P<br />
<br />
8:52:59 PM <@tl_lim> Just a console break-up board<br />
<br />
8:53:26 PM <@tl_lim> the trigger UART console signal out from USB-C port<br />
<br />
8:53:32 PM <@UniversalSuperBox> If you put the PineNote near a CT scanner, it shorts out because all the reed switches trigger<br />
<br />
8:53:54 PM <@tl_lim> s/the/that<br />
<br />
8:54:07 PM <dsimic> it shors out and the UART gets routed out :)<br />
<br />
8:54:17 PM <dsimic> * shorts<br />
<br />
8:54:23 PM <@UniversalSuperBox> Task failed successfully<br />
<br />
8:54:24 PM <@UniversalSuperBox> anyway<br />
<br />
8:54:48 PM <@tl_lim> any simple proposal welcome.<br />
<br />
8:55:06 PM <dsimic> would drilling a hole in the case be an option?<br />
<br />
8:55:09 PM <@smaeul> I think we are talking about the same thing: use a cable/breakout board to trigger DAM, which switches some pins to carry the UART<br />
<br />
8:55:33 PM <@tl_lim> DAM is too much<br />
<br />
8:55:45 PM <dsimic> what other options are there?<br />
<br />
8:55:53 PM <@tl_lim> just need two signals, T๐and RxD<br />
<br />
8:56:14 PM <@MartijnBraam> No headphone jack on the pinenote?<br />
<br />
8:56:20 PM <@tl_lim> no<br />
<br />
8:56:24 PM <@smaeul> but how do you know when to enable UART vs normal USB ?<br />
<br />
8:57:05 PM <@tl_lim> the UART signal only output when this break-out board plug into teh USB-C connector<br />
<br />
8:57:17 PM <@tl_lim> s/output/available<br />
<br />
8:58:02 PM <@tl_lim> normal USB-C cable plug in to USB-C connector, then normal USB behavior<br />
<br />
8:58:06 PM <@UniversalSuperBox> What you're describing is DAM. Has the team already replied that it isn't possible?<br />
<br />
8:59:03 PM <@tl_lim> brb in 30m mins, I wil keep wtach the chat. Just need to have a conference call.<br />
<br />
9:04:20 PM <@tl_lim> back now<br />
<br />
9:05:25 PM <@tl_lim> check out this: https://github.com/ddvk/remarkable2-recovery<br />
<br />
9:06:41 PM <dsimic> that still requires additional logic on the host side<br />
<br />
9:08:17 PM <@UniversalSuperBox> Mhmm, that's using both the USB-C port and the pogo pins on the reMarkable for recovery. Seems like they exposed the iMX's recovery pins on B8 (SBU2) of the USB-C cable. So that step is the same as our magnetic switch.<br />
<br />
9:08:24 PM <@UniversalSuperBox> Then UART comes out the pogo pins, which we don't have.<br />
<br />
9:08:40 PM <@UniversalSuperBox> (along with the iMX flash mode)<br />
<br />
9:09:44 PM <dsimic> how about this: we must have additional logic on the host side (i.e. some board changes), so the primary question should be whether we want to take the route of doing it in the standard way (i.e. DAM), or we want to invent and implement some non-standard way?<br />
<br />
9:10:25 PM <dsimic> yeah, they use pogo pins, which the PineNote doesn't have<br />
<br />
9:10:37 PM <@UniversalSuperBox> I've done more careful reading of the USB-C spec: https://www.usb.org/document-library/usb-type-cr-cable-and-connector-specification-revision-21<br />
<br />
9:10:40 PM <@smaeul> the willsemi chip looks extremely similar to this chip (same pinout), except the FUSB303B also uses the "ROLE" pin as a debug mode output: https://www.onsemi.com/pdf/datasheet/fusb303b-d.pdf<br />
<br />
9:10:43 PM <@UniversalSuperBox> See appendix B<br />
<br />
9:11:26 PM <dsimic> I can't access the spec<br />
<br />
9:11:28 PM <@tl_lim> purchase TI chip is a nightmere at current severe chip shortage situation.<br />
<br />
9:11:44 PM <dsimic> there might be other ICs that do the same<br />
<br />
9:12:23 PM <dsimic> UniversalSuperBox: could you, please, send the spec?<br />
<br />
9:13:17 PM <dsimic> ah, got it<br />
<br />
9:13:55 PM <@smaeul> tl_lim: any idea about the ON semi chip? it would be pretty close to drop-in compatible.<br />
<br />
9:14:43 PM <UnivrslSuprBox> https://usercontent.irccloud-cdn.com/file/PGeULRZK/USB%20Type-C%20Spec%20R2.1%20-%20May%202021.pdf<br />
<br />
9:14:44 PM <@tl_lim> That is possible, due to mux chip can be simply has other alternative chip or even using MOSFET<br />
<br />
9:15:38 PM <@smaeul> yes, it looks like 3-way (USB 2.0, Audio, UART) switch chips are available<br />
<br />
9:15:40 PM <@tl_lim> PineNote only use USB 2.0 signals<br />
<br />
9:17:19 PM <@UniversalSuperBox> Or audio<br />
<br />
9:17:39 PM <@UniversalSuperBox> But with a three-way switch, our own adapter board would break out UART.<br />
<br />
9:17:41 PM <@Icenowy> are you trying to use Debug Accessory mode?<br />
<br />
9:17:57 PM <@tl_lim> hi icenoway<br />
<br />
9:18:11 PM <@UniversalSuperBox> We're trying to get closed-case UART on a device with only a USB-C port. If that involves DAM, that's what we should use. (re @Icenowy: are you trying to use Debug Accessory mode?)<br />
<br />
9:18:13 PM <@tl_lim> how to implement UART way?<br />
<br />
9:18:27 PM <@Icenowy> well I think DAM too<br />
<br />
9:18:46 PM <@Icenowy> but I have no idea what can implement it<br />
<br />
9:19:41 PM <dsimic> well, we found a few ICs that can do that, or at least should do that, according to the datasheets<br />
<br />
9:19:50 PM <@tl_lim> interest to know more USB-C UART implementation<br />
<br />
9:20:07 PM <dsimic> how about this: we must have additional logic on the host side (i.e. some board changes), so the primary question should be whether we want to take the route of doing it in the standard way (i.e. DAM), or we want to invent and implement some non-standard way?<br />
<br />
9:21:07 PM <@tl_lim> this is just for console UART, don't mind standard or non-standard way<br />
<br />
9:21:26 PM <dsimic> but we need board changes anyway<br />
<br />
9:21:30 PM <@Icenowy> I think there could be some hardware that already utilizes DAM<br />
<br />
9:21:36 PM <@smaeul> dsimic: for sure the standard way is safest, so we should do that if at all possible<br />
<br />
9:21:38 PM <@Icenowy> e.g. Google Pixels w/o 3.5mm ?<br />
<br />
9:21:49 PM <dsimic> smaeul: I agree 100%<br />
<br />
9:22:04 PM <@tl_lim> I may not<br />
<br />
9:22:07 PM <@UniversalSuperBox> The most well-known DAM device is the Chrome OS SuzyQable. that's used on the Pixel 2 and up, and Chromebooks after the Pixelbook<br />
<br />
9:22:24 PM <@Icenowy> well yes, use the standard way can prevent incompatibility with 3rd party Type-C peripherals (re @p64protocolbot: <@smaeul> dsimic: for sure the standard way is safest, so we should do that if at all possible)<br />
<br />
9:22:27 PM <@tl_lim> as stated, I just look for a simple way to bring up UART signal.<br />
<br />
9:23:15 PM <@Icenowy> it could be problematic to try to do things unstandardly (re @tl_lim: as stated, I just look for a simple way to bring up UART signal.)<br />
<br />
9:23:17 PM <@tl_lim> I want to minimize the change as little as possible<br />
<br />
9:23:22 PM <@Icenowy> considering compatibility<br />
<br />
9:23:37 PM <dsimic> I also want to make as few board changes as possible<br />
<br />
9:24:26 PM <@Icenowy> add a switch like what PineTab does?<br />
<br />
9:24:31 PM <@smaeul> UniversalSuperBox: SuzyQable would require a USB<->UART adapter inside the device<br />
<br />
9:24:34 PM <@UniversalSuperBox> Case changes are not possible<br />
<br />
9:24:49 PM <@tl_lim> if the DMA way is simple, I will consider. If not a good way and then developer just need to open the back case.<br />
<br />
9:25:27 PM <dsimic> using DMA would require to add one IC and replace another, basically<br />
<br />
9:25:45 PM <@tl_lim> if TI chip, then NO<br />
<br />
9:25:46 PM <dsimic> (if we can find the right ICs that are currently available)<br />
<br />
9:26:16 PM <dsimic> * DAM<br />
<br />
9:26:16 PM <@Diego> ยฟis it posible to out uart in usb-c audio adapter mode?<br />
<br />
9:26:51 PM <@UniversalSuperBox> It is non-standard so it poses at least a minimal risk to anything plugged in to the PineNote. (re @Diego: ยฟis it posible to out uart in usb-c audio adapter mode?)<br />
<br />
9:26:55 PM <@smaeul> Diego: that's the same thing as DAM, just with resistors pulled the other way<br />
<br />
9:26:58 PM <dsimic> that would also require some IC to do the switch, and would also be non-standard<br />
<br />
9:27:55 PM <@smaeul> I happen to be looking at ON semi's website at the moment, so there may be other options, but DAM would be doable by replacing the Type-C chip with this: https://www.onsemi.com/pdf/datasheet/fusb303b-d.pdf and the 2-way mux with a 3-way mux like this: https://www.onsemi.com/pdf/datasheet/fsa1153-d.pdf<br />
<br />
9:28:02 PM <@tl_lim> when thinking on UART console thru USB-C, there is assumption is not a standard<br />
<br />
9:28:36 PM <@tl_lim> FUSB303B is a nightmere chip to purchase.<br />
<br />
9:28:55 PM <@smaeul> ok, good to know<br />
<br />
9:29:26 PM <@tl_lim> I have no interest PineNote delay for few months due to we try to do UART thru USB-C.<br />
<br />
9:30:13 PM <@tl_lim> BTW, Pinecil currently using FUSB303<br />
<br />
9:30:44 PM <dsimic> what's VCC_HALL_3V3 in the schematic?<br />
<br />
9:30:52 PM <@Icenowy> I think it's 302?<br />
<br />
9:30:57 PM <@Icenowy> for Pinecil<br />
<br />
9:31:01 PM <@Icenowy> (and PBP<br />
<br />
9:31:25 PM <@tl_lim> sorry 302, my bad<br />
<br />
9:33:48 PM <dsimic> well, here's a crazy option, if all else fails... add a magnetic switch that cuts off both VDD and VUSD from WUSB3801 and connects RX and TX to the CC1 and CC2 pins<br />
<br />
9:34:21 PM <dsimic> it might even work :)<br />
<br />
9:34:48 PM <@smaeul> it would be better to use the SBU pins -- they are already brought to the mainboard but unused<br />
<br />
9:34:53 PM <@UniversalSuperBox> Nah, if we were going to do something dumb, we could route it over SBU<br />
<br />
9:35:13 PM <@UniversalSuperBox> But even that could end up blowing out a poorly designed device on the other end, or the PineNote itself.<br />
<br />
9:35:22 PM <@UniversalSuperBox> If we're going to dumb options, let's not do it at all<br />
<br />
9:35:38 PM <dsimic> I'm glad that my crazy option is considered dumb :)<br />
<br />
9:35:50 PM <@tl_lim> Just FYI, FUSB303 totally no stock : <br />
<br />
9:36:28 PM <dsimic> I agree, either in the standard way or not at all<br />
<br />
9:36:36 PM <@UniversalSuperBox> Oh, sorry. I should be more careful with my words dsimic<br />
<br />
9:37:03 PM <dsimic> oh no, I'm really happy that it was called dumb :)<br />
<br />
9:37:10 PM <@tl_lim> PineNote just only USB 2, teh USB 3 signal is not use<br />
<br />
9:37:55 PM <dsimic> yeah, but we can't connect something randomly to the unused pins<br />
<br />
9:38:04 PM <@UniversalSuperBox> But the moment some terrible USB hub starts sending 5V over the USB 3.0 pins for "device detection" we kill the RK3566<br />
<br />
9:38:12 PM <@tl_lim> we just need a simple way the console break out board can trigger mux circuit and output the UART signals<br />
<br />
9:38:55 PM <@UniversalSuperBox> Well, the standard way to do that would be DAM. If both CC1 and CC2 are pulled high (or low), all of the USB-C pins switch to a vendor-specified pinout.<br />
<br />
9:39:12 PM <dsimic> yeah, DAM it is<br />
<br />
9:39:18 PM <@UniversalSuperBox> It's not possible to have CC1 and CC2 pulled during normal use because standard USB-C cables only have one of the two connected.<br />
<br />
9:40:09 PM <@tl_lim> may be using the DAM way to trigger the mux and teh UART sign output from 2 USB 3.0 pin which current not been used<br />
<br />
9:40:17 PM <@smaeul> assuming DAM is not possible, something simpler to control MOSFETs between UART and SBU would work, as long as it didn't trigger accidentally<br />
<br />
9:40:29 PM <dsimic> tl_lim: yes, we could do that with DAM<br />
<br />
9:40:29 PM <@UniversalSuperBox> If that detection of both CC1 and CC2 can be done on an external mux circuit, it seems shaky but usable.<br />
<br />
9:41:03 PM <@tl_lim> prefer to use USB 3 signal due to not in use at PineNote<br />
<br />
9:41:15 PM <@UniversalSuperBox> When DAM is detected, the USB-C port disconnects all standard USB-C signals and connects any signals you want to the specified pins.<br />
<br />
9:41:40 PM <dsimic> it's up to the vendor to use the pins in any way in DAM, but we must not have the UART connected at all when DAM isn't detected <br />
<br />
9:41:42 PM <@UniversalSuperBox> Just like when audio mode is detected, everything is disconnected and the audio stuff is connected.<br />
<br />
9:42:03 PM <dsimic> but we can keep USB 2.0 signals conected in DAM, right?<br />
<br />
9:42:07 PM <@tl_lim> no need to disconnect, just route uart signal to two unused usb3 pins<br />
<br />
9:42:12 PM <dsimic> that's our OEM spec :)<br />
<br />
9:42:26 PM <dsimic> * connected<br />
<br />
9:42:53 PM <dsimic> we're free to connect anything anywhere in DAM, so we can leave the USB 2.0 pins connected, but actually not use them<br />
<br />
9:43:03 PM <@tl_lim> when both CC1 and CC2 detected high<br />
<br />
9:43:17 PM <dsimic> i.e. in the DAM<br />
<br />
9:43:40 PM <dsimic> but we must not have the UART connected at all to the USB pins when DAM isn't detected <br />
<br />
9:43:49 PM <@tl_lim> just 74125 will do<br />
<br />
9:43:52 PM <dsimic> switching UART should be very simple<br />
<br />
9:44:25 PM <dsimic> so we just need an IC that detects DAM, or a way to implemenent that "by hand"<br />
<br />
9:44:39 PM <dsimic> problem solved, right? :)<br />
<br />
9:44:48 PM <@tl_lim> when both cc1 and cc2 not in logic hi, the gate is floating.<br />
<br />
9:45:35 PM <dsimic> but the existing WUSB3801 must not be affected<br />
<br />
9:45:40 PM <@tl_lim> I try to use USB 3 signal due to not use and less compatibility issue<br />
<br />
9:46:14 PM <dsimic> using USB 3.0 pins is fine, but the UART must be disconnected from them when DAM isn't detected<br />
<br />
9:46:24 PM <dsimic> and the USB 2.0 bus an remain connected in DAM<br />
<br />
9:46:28 PM <dsimic> * can<br />
<br />
9:46:41 PM <dsimic> that's our vendor DAM layout :<br />
<br />
9:46:43 PM <dsimic> :)<br />
<br />
9:47:01 PM <@UniversalSuperBox> But would we hit an issue where the existing WUSB3801 would get confused in that state?<br />
<br />
9:47:03 PM <dsimic> does everyone agree on that?<br />
<br />
9:47:06 PM <@tl_lim> no need to flip, the UART console break out board only works one way which component layer face up<br />
<br />
9:47:16 PM <@tl_lim> there is no WUSB3801<br />
<br />
9:47:22 PM <@UniversalSuperBox> oh, what was it called<br />
<br />
9:47:39 PM <dsimic> there is WUSB3801 in the PineNote already<br />
<br />
9:47:45 PM <dsimic> U9008<br />
<br />
9:47:49 PM <@tl_lim> code name: Dalton Operation ๐<br />
<br />
9:48:16 PM <dsimic> anyway, the existing WUSB3801 must not be affected<br />
<br />
9:48:46 PM <dsimic> by the additional CC/DAM detection logic<br />
<br />
9:48:59 PM <@UniversalSuperBox> Yeah, I'm not crazy. The schematic has a WUSB3801 on it.<br />
<br />
9:49:01 PM <@smaeul> The WUSB3801 detects DAM already, so it should be fine as long as our "CC high" detection logic doesn't mess up Rp/Rn detection<br />
<br />
9:49:09 PM <dsimic> right<br />
<br />
9:49:46 PM <@tl_lim> just a simple AND logic on cc1/cc2 and 74125 type for Tx and Rx.<br />
<br />
9:50:15 PM <@UniversalSuperBox> I would guess that WUSB3801 powers VCC_HALL_3V3 so that in a no-battery case, plugging in power with the magnet switch triggered would still cause the RK3566 to go into maskrom flash mode.<br />
<br />
9:50:36 PM <dsimic> VCC_HALL_3V3 is a regulated supply, AFAICT<br />
<br />
9:50:54 PM <@UniversalSuperBox> (to answer the earlier question)<br />
<br />
9:51:05 PM <@smaeul> yeah, it's the other way around. VCCHALL3V3 powers the WUSB3801<br />
<br />
9:51:33 PM <@UniversalSuperBox> k<br />
<br />
9:52:50 PM <@UniversalSuperBox> > just a simple AND logic on cc1/cc2 and 74125 type for Tx and Rx.<br />
<br />
9:52:58 PM <@UniversalSuperBox> ^ Will this work?<br />
<br />
9:53:27 PM <dsimic> 74152 should work for the UART<br />
<br />
9:53:35 PM <dsimic> * 74125<br />
<br />
9:54:01 PM <@tl_lim> for MOSFET<br />
<br />
9:54:28 PM <@tl_lim> just give teh design engiener an idea and they figure out ๐<br />
<br />
9:54:31 PM <dsimic> but for the AND logic on CC1 and CC2, I'm not 100% sure how to do that without affecting the WUSB3801 (U9008)<br />
<br />
9:55:09 PM <dsimic> but the board designer should be able to figure that out :)<br />
<br />
9:56:10 PM <@tl_lim> the worst case is OTG and uart console cannot works at same time, and I don't think this is a big issue<br />
<br />
9:56:21 PM <@UniversalSuperBox> That would honestly be my expected state<br />
<br />
9:57:25 PM <@tl_lim> I just hate to ask developers using tool to open the PineNote backcase when need to access to the console UART. Just think a simple way<br />
<br />
9:57:31 PM <@UniversalSuperBox> and if you really want to ruin your engineers' day, tell them to disconnect all the USB pins and route the microSD pins when CC1 and CC2 are both connected ๐<br />
<br />
9:58:16 PM <@UniversalSuperBox> But y'know, whatever keeps the cost acceptable works.<br />
<br />
9:58:56 PM <dsimic> when the console cable is connected, nothing else works<br />
<br />
9:59:05 PM <dsimic> that's the expected behavior<br />
<br />
9:59:17 PM <dsimic> I mean, nothing else on the USB connector works :)<br />
<br />
9:59:17 PM <@tl_lim> appreciate and thanks on brainstorming.<br />
<br />
9:59:40 PM <@UniversalSuperBox> It is indeed expected that when CC1 and CC2 are shorted, USB stops working. To the spec, that is an acceptable outcome.<br />
<br />
9:59:51 PM <@UniversalSuperBox> Sorry, s/shorted/pulled high or low/<br />
<br />
10:00:14 PM <@tl_lim> then I just need to create a small breakout board and give away on the first batch PineNote<br />
<br />
10:00:46 PM <dsimic> also, when the serial console cable is connected, our vendor-defined DAM pinout becomes effective<br />
<br />
10:00:59 PM <dsimic> + some board changes<br />
<br />
10:01:04 PM <@UniversalSuperBox> Right. Having UART on it is most important. Having microSD and USB 2.0 as well would be really cool, but not a requirement.<br />
<br />
10:01:26 PM <@UniversalSuperBox> Depending on how debug you want the debug cable to be :)<br />
<br />
10:01:26 PM <dsimic> we could have microSD as well<br />
<br />
10:01:34 PM <@UniversalSuperBox> could, not needed<br />
<br />
10:01:41 PM <dsimic> yeah<br />
<br />
10:01:53 PM <dsimic> can an internal microSD slot be added?<br />
<br />
10:02:08 PM <@UniversalSuperBox> That's an idea that's been floated. At least a header on the board.<br />
<br />
10:02:37 PM <@tl_lim> microSD needs more pins.<br />
<br />
10:02:54 PM <dsimic> can we pull that idea low or high, so it isn't floating? :)<br />
<br />
10:05:11 PM <dsimic> hmm, just a second, please...<br />
<br />
10:05:42 PM <@tl_lim> I just focus on UART console route out possibility<br />
<br />
10:06:44 PM <@tl_lim> BTW, just lets you knows a lot of cheap USB-C cable in market short cc1 and cc2 together to save a wire.<br />
<br />
10:07:04 PM <dsimic> https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode ... yeah, we can use USB 3.0 pins for UART, and we're left with eight more unused pins to play with<br />
<br />
10:07:56 PM <@tl_lim> who provid ethe cable?<br />
<br />
10:08:19 PM <dsimic> we can have microSD as well, there are enough free pins :)<br />
<br />
10:08:45 PM <@smaeul> ...if you modify the cable connecting the mainboard to the USB board, and the USB board<br />
<br />
10:09:06 PM <@tl_lim> too much job<br />
<br />
10:09:27 PM <dsimic> those cables are costly to modify<br />
<br />
10:09:40 PM <@smaeul> exactly, please consider the scope of what you're asking for, not just if it's possible<br />
<br />
10:09:50 PM <dsimic> of course<br />
<br />
10:09:54 PM <@UniversalSuperBox> Will an internally-mounted breakout cable for microSD be available in the store @tl_lim?<br />
<br />
10:09:58 PM <dsimic> so, UART it is :)<br />
<br />
10:10:22 PM <@tl_lim> just UART<br />
<br />
10:10:44 PM <@UniversalSuperBox> NOT usb-c, only an internal ribbon cable to a microSD card slot (re @UniversalSuperBox: Will an internally-mounted breakout cable for microSD be available in the store @tl_lim?)<br />
<br />
10:10:48 PM <@tl_lim> the people can use a USB-C breakout board that alreasdy available in market<br />
<br />
10:11:35 PM <@UniversalSuperBox> Yes<br />
<br />
10:11:44 PM <dsimic> I don't think that the microSD lines are routed at all on the board<br />
<br />
10:11:56 PM <@tl_lim> currently not<br />
<br />
10:12:08 PM <@UniversalSuperBox> But that's something pgwipeout made clear we should really do<br />
<br />
10:12:22 PM <dsimic> then we'd have no use of a ribbon cable for microSD, without a board redesign<br />
<br />
10:12:30 PM <@tl_lim> the product board will have microSD signal bring to a flex connector<br />
<br />
10:12:40 PM <dsimic> ah, that's fine<br />
<br />
10:13:02 PM <@UniversalSuperBox> Were there any other signals coming out to flex connectors on the final revision? (re @tl_lim: the product board will have microSD signal bring to a flex connector)<br />
<br />
10:14:36 PM <@tl_lim> other will be easter egg hunting games</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11105PineNote2021-08-20T02:01:58Z<p>UniversalSuperBox: </p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Built in stereo speakers<br />
* 4 x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
* [[PineNote/Hardware_Changes/Closed_Case_UART]]<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
== Hardware troubleshooting guide ==<br />
At present, nothing is available.<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote/Hardware_Changes/Closed_Case_UART&diff=11104PineNote/Hardware Changes/Closed Case UART2021-08-20T02:01:00Z<p>UniversalSuperBox: Created page with "Closed case debugging was brought up during a week of community schematic review of the PineNote. This page documents the discussion of this proposed issue and its resolution...."</p>
<hr />
<div>Closed case debugging was brought up during a week of community schematic review of the PineNote. This page documents the discussion of this proposed issue and its resolution.<br />
<br />
Dates on this page are relative to UTC-5.<br />
<br />
== Background ==<br />
<br />
When debugging bootloader and kernel initialization on a new hardware platform, a hardware UART is indispensable. The PineNote 1.1 required taking the device apart to access a hardware UART broken out on the motherboard. This did not seem tenable long-term, as developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART.<br />
<br />
Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
== Discussion ==<br />
<br />
=== August 15, 2021 ===<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
<br />
=== August 16-18, 2021 ===<br />
<br />
There were concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. This may cause the PineNote to output 3.3v UART to a device that isn't expecting it, assuming the two are plugged together with a nonstandard cable. This seems unfounded (or not enough of a problem to worry about on a large scale), since the USB-C specification states in section B.2.3.1, "The general concept for setting up a valid connection between a DTS and TS is based on being able to detect the typical USB Type-C termination resistances. However, detecting a Debug Accessory Mode connection requires that both CC pins must detect a pull-up (Rp) or pull-down (Rd) termination. A USB Type-C Cable does not pass both CC wires so a receptacle to receptacle Debug Accessory Mode connection cannot be detected."<br />
<br />
There were concerns that checking CC1 and CC2 being pulled high was not strictly to USB-C standard, as detecting them being pulled low is mentioned in the standard. However, detecting a pull-up condition is all that is required. According to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution.<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== Resolution ==<br />
<br />
[[File:PineNote USB-C DAM Schematic Addition.png|thumb|This proposed circuitry is added to the PineNote v1.1 schematic]]<br />
<br />
On August 19, 2021, TL posted the results of the hardware team's efforts. This includes [[:File:PineNote USB-C DAM Schematic Addition.png]], shown on this page, as well as the following additional documentation:<br />
<br />
* [[File:NS5S1153-D.PDF|Datasheet for ON Semiconductor NS5S1153 USB-C USB 2.0 and Audio Switch.]]<br />
<br />
Additionally, the hardware team proposed designing a breakout board with pull-up resistors on CC1 and CC2 and the appropriate UART signals routed to headers on the board. Then a developer can bring their own USB TTL adapter. They almost definitely have at least one, or could access one for a low price.<br />
<br />
dsimic commented that this proposed layout meant that a Google-designed SuzyQable would '''not''' work for debugging the PineNote. This was deemed acceptable, as long as it is clear to developers that the combination of PineNote and SuzyQable will not result in any useful debugging abilities.<br />
<br />
Caleb commented that the Google Pixel series of devices bring out UART over the SB1 and SB2 pins on the USB-C connector. It was surmised that copying this layout would allow reusing hardware that developers already have, however there are no harnesses on the market that directly break out this interface. Instead, it seems that most developers use a USB-C breakout board and stuff wires in the appropriate place when needed[https://github.com/Peter-Easton/android-debug-cable-howto]. A similar approach could be taken with the proposed PineNote solution if someone did not wish to purchase the breakout board.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=File:NS5S1153-D.PDF&diff=11103File:NS5S1153-D.PDF2021-08-20T01:37:38Z<p>UniversalSuperBox: Datasheet for ON Semiconductor NS5S1153 USB-C USB 2.0 and Audio Switch.</p>
<hr />
<div>== Summary ==<br />
Datasheet for ON Semiconductor NS5S1153 USB-C USB 2.0 and Audio Switch.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=File:PineNote_USB-C_DAM_Schematic_Addition.png&diff=11102File:PineNote USB-C DAM Schematic Addition.png2021-08-20T01:29:53Z<p>UniversalSuperBox: Proposed addition to the PineNote 1.1 schematic to allow for closed case debugging via UART out on the USB-C port. Prevents UART being exposed unless both CC1 and CC2 are pulled high on the port at the same time.</p>
<hr />
<div>== Summary ==<br />
Proposed addition to the PineNote 1.1 schematic to allow for closed case debugging via UART out on the USB-C port. Prevents UART being exposed unless both CC1 and CC2 are pulled high on the port at the same time.<br />
== Licensing ==<br />
{{subst:Unknown_copyright}}</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11097PineNote2021-08-19T04:13:31Z<p>UniversalSuperBox: forgot a bit of the quote :)</p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There were concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. This may cause the PineNote to output 3.3v UART to a device that isn't expecting it, assuming the two are plugged together with a nonstandard cable. This seems unfounded (or not enough of a problem to worry about on a large scale), since the USB-C specification states in section B.2.3.1, "The general concept for setting up a valid connection between a DTS and TS is based on being able to detect the typical USB Type-C termination resistances. However, detecting a Debug Accessory Mode connection requires that both CC pins must detect a pull-up (Rp) or pull-down (Rd) termination. A USB Type-C Cable does not pass both CC wires so a receptacle to receptacle Debug Accessory Mode connection cannot be detected."<br />
<br />
There were concerns that checking CC1 and CC2 being pulled high was not strictly to USB-C standard, as detecting them being pulled low is mentioned in the standard. However, detecting a pull-up condition is all that is required. According to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution.<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11096PineNote2021-08-19T04:06:39Z<p>UniversalSuperBox: </p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There were concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. This may cause the PineNote to output 3.3v UART to a device that isn't expecting it, assuming the two are plugged together with a nonstandard cable. This seems unfounded (or not enough of a problem to worry about on a large scale), since the USB-C specification states in section B.2.3.1, "The general concept for setting up a valid connection between a DTS and TS is based on being able to detect the typical USB Type-C termination resistances. However, detecting a Debug Accessory Mode connection requires that both CC pins must detect a pull-up (Rp) or pull-down (Rd) termination. A USB Type-C Cable does not pass both CC wires so a receptacle to receptacle Debug Accessory Mode connection"<br />
<br />
There were concerns that checking CC1 and CC2 being pulled high was not strictly to USB-C standard, as detecting them being pulled low is mentioned in the standard. However, detecting a pull-up condition is all that is required. According to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution.<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11095PineNote2021-08-19T03:58:58Z<p>UniversalSuperBox: Fix typo</p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There are concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. This may cause the PineNote to output 3.3v UART to a device that isn't expecting it, assuming the two are plugged together with a nonstandard cable.<br />
<br />
There were concerns that checking CC1 and CC2 being pulled high was not strictly to USB-C standard, as detecting them being pulled low is mentioned in the standard. However, detecting a pull-up condition is all that is required. According to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution.<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11094PineNote2021-08-19T03:58:44Z<p>UniversalSuperBox: Rewrite strikethrough section as introduction to paragraph,</p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There are concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. This may cause the PineNote to output 3.3v UART to a device that isn't expecting it, assuming the two are plugged together with a nonstandard cable.<br />
<br />
There were concerns that checking CC1 and CC2 being pulled high was not strictly to USB-C standard, as detecting them being pulled low is mentioned in the standard. However,h etecting a pull-up condition is all that is required. According to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution.<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11093PineNote2021-08-19T03:54:29Z<p>UniversalSuperBox: Update concern about CC1 and CC2 being high or low</p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There were concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire.<br />
<br />
Detecting a pull-up condition is all that is required, as according to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution. <del>There is an additional concern (not in the IRC logs) that only checking for CC1 and CC2 being pulled high is not technically within USB-C DAM specifications, since detecting CC1 and CC2 being pulled high ''or'' low is mentioned.<del><br />
<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11092PineNote2021-08-19T03:32:26Z<p>UniversalSuperBox: </p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There were concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. There is an additional concern (not in the IRC logs) that only checking for CC1 and CC2 being pulled high is not technically within USB-C DAM specifications, since detecting CC1 and CC2 being pulled high ''or'' low is mentioned.<br />
<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11091PineNote2021-08-19T03:15:38Z<p>UniversalSuperBox: Add information about USB-C DAM discussion for posterity.</p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
<br />
=== Software ===<br />
<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
=== Hardware ===<br />
<br />
This section includes discussions and their results regarding hardware changes to the PineNote.<br />
<br />
==== Closed-Case UART ====<br />
<br />
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.<br />
<br />
We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.<br />
<br />
This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.<br />
<br />
There were concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. There is an additional concern (not in the IRC logs) that only checking for CC1 and CC2 being pulled high is not technically within USB-C DAM specifications, since detecting CC1 and CC2 being pulled high ''or'' low is mentioned.<br />
<br />
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineNote&diff=11089PineNote2021-08-19T02:32:05Z<p>UniversalSuperBox: Move PineNote "hero image" off to the right side</p>
<hr />
<div>[[File:PineNote-1.jpg|frame]]<br />
<br />
The PineNote is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU.<br />
<br />
== Specification ==<br />
<br />
[[File:PineNote_Pen_function.jpg|300px|right]]<br />
[[File:PineNote_Cover-1.jpg|300px|right]]<br />
<br />
=== General Information ===<br />
* Dimensions: 191.1x232.5x7.4mm<br />
* Weight: 438g<br />
<br />
=== Core ===<br />
* CPU: RK3566 1.8GHz 64-bit quad-core A55<br />
* GPU: MALI G52 2EE<br />
* System memory: 4GB LPDDR4<br />
* Flash: 128GB eMMC<br />
<br />
=== E-ink Display ===<br />
* Size: 10.3"<br />
* Resolution: 1404x1872<br />
* DPI: 227<br />
* Grayscale: 16<br />
* Front Light: 36 level cold and warm <br />
* Capacitive multi-touch panel<br />
* EMR pen digitizer<br />
<br />
=== Network ===<br />
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac<br />
* Bluetooth: 5.0<br />
<br />
=== Audio ===<br />
* Build in stereo speaker<br />
* 4x DMIC microphone<br />
<br />
=== Sensor ===<br />
* G-Sensor for portrait and landscape sensing<br />
<br />
=== Power ===<br />
* 4000mAH LiPo battery<br />
* DC 5V @ 3A USB-C connector<br />
<br />
=== Accessories ===<br />
* Optional EMR pen with magnetic attachment (included in the first production batch)<br />
* Optional Cover (included in the first production batch)<br />
<br />
<br />
== Software and OS Image Downloads ==<br />
<br />
* Not yet available<br />
<br />
<br />
== SoC and Memory Specifications ==<br />
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]<br />
[[File:RK3566_icon.png|right]]<br />
<br />
=== CPU Architecture ===<br />
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]<br />
* AArch32 for full backwards compatibility with ARMv7<br />
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation<br />
* Includes VFP hardware to support single and double-precision operations<br />
* ARMv8 Cryptography Extensions<br />
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core<br />
* 512KB unified system L3 cache<br />
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support<br />
* [https://www.cnx-software.com/2020/12/01/rockchip-rk3568-processor-to-power-edge-computing-and-nvr-applications 22nm process, believed to be FD-SOI]<br />
<br />
=== GPU (Graphics Processing Unit) Capabilities ===<br />
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]<br />
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop <br />
* 128KB L2 Cache configurations<br />
* Supports OpenGL ES 1.1, 2.0, and 3.2<br />
* Supports Vulkan 1.0 and 1.1<br />
* Supports OpenCL 2.0 Full Profile<br />
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency<br />
* Supports 38.4 GLOP/s when at 800MHz clock frequency <br />
<br />
=== NPU (Neural Processing Unit) Capabilities ===<br />
* Neural network acceleration engine with processing performance of up to 0.8 TOPS<br />
* Supports integer 8 and integer 16 convolution operations<br />
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet<br />
<br />
=== System Memory ===<br />
* RAM Memory : 4GB LPDDR4.<br />
* Flash Memory: 128GB eMMC<br />
<br />
== PineNote Information, Schematics, and Certifications ==<br />
* The early release schematic just for reference only and used by developers who received the prototype. <br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]<br />
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1-REF-TOP-20210726.pdf PineNote early released ver 1.1 20210726 PCB Connector placement PDF file]<br />
<br />
* Certifications:<br />
** Not yet available<br />
<br />
== Datasheets for Components and Peripherals ==<br />
* Rockchip RK3566 SoC information:<br />
** [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, already got release permission from Rockchip]<br />
* Rockchip RK817 PMU (Power Management Unit) Information:<br />
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]<br />
* LPDDR4 (200 Balls) SDRAM:<br />
** ---<br />
* eMMC information:<br />
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G] <br />
* E-ink Panel information:<br />
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ES103TC2 Glass Panel Specification]<br />
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]<br />
* Touch Screen information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]<br />
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module<br />
* WiFi/BT module info:<br />
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]<br />
* G Sensor info:<br />
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]<br />
* Audio Amplifier information:<br />
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]<br />
<br />
<br />
== Development Efforts ==<br />
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC<br />
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver<br />
<br />
== BSP Linux SDK ==<br />
<br />
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===<br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed<br />
** File Size: 32.67.00GB<br />
<br />
== Android SDK ==<br />
<br />
=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===<br />
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC. <br />
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]<br />
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672<br />
** File Size: 72.88GB<br />
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]<br />
<br />
[[Category:PineNote]] [[Category:Rockchip RK3566]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineTab/Early-Adopter&diff=7119PineTab/Early-Adopter2020-09-15T20:19:15Z<p>UniversalSuperBox: </p>
<hr />
<div>The PineTab Early Adopter edition was the first hardware revision of the PineTab which shipped to customers. Shipping began on September 6, 2020.<br />
<br />
== Software ==<br />
<br />
The device shipped with a beta build of Ubuntu Touch by UBports. This build is available to download at https://ci.ubports.com/job/rootfs/job/rootfs-pinetab-systemimage/18/. It has the following problems which are software, not hardware, issues:<br />
<br />
* The mouse fails to move around the entire screen. It is stuck in an 800px horizontal box.<br />
* It is not possible to enable Bluetooth<br />
* Cameras do not function<br />
* Portrait mode does not function<br />
* The external keyboard is not always detected<br />
* There is a faint crackling noise on startup<br />
* Pasting an item on File Manager after Copy/Cut reboots the operating system<br />
* GUI apps with Libertine are not working, because of missing bits between wayland and Libertine<br />
<br />
The first-time setup wizard advises the user to unplug the keyboard dock (avoiding the mouse issues) and update the system. Unfortunately, as of this update to this page (September 8, 2020) this will not fix any of the issues above.<br />
<br />
=== 16GB/64GB storage software error ===<br />
<br />
The image installed on the device was sized for a 16GB (~14GiB) eMMC, but the PineTab shipped with a 64GB (~58GiB) eMMC chip installed. This means that the "Storage" page in the "About" section of Ubuntu Touch System Settings will show total storage as 14.0GiB until the partition table on the device is edited. <br />
<br />
This is fixed by an update to Ubuntu Touch released to the Stable channel on September 15, 2020. The image's tag is "2020-09-12", visible in Settings -> About -> OS.<br />
<br />
=== Installing using apt ===<br />
<br />
Installing software on the read-only root filesystem is unsupported on Ubuntu Touch. You should be able to find updates in System Settings -> Updates and new applications in the OpenStore. If you would like to install and use terminal software from the Ubuntu repositories, see [https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html Run desktop applications in the UBports Documentation] to set up a Libertine container. Unfortunately, graphical software does not yet work through Libertine. This issue is tracked as [https://github.com/ubports/libertine/issues/68 ubports/libertine#68]<br />
<br />
=== Enabling ssh ===<br />
Naturally, you should be wary of enabling ssh for security reasons but everything is there. Almost.<br />
<br />
Edit /etc/ssh/sshd_config<br />
<br />
Change the following:<br />
* PasswordAuthentication yes<br />
* ChallengeResponseAuthentication yes<br />
<br />
Then:<br />
/etc/init.d/sshd start<br />
<br />
Use user phablet along with your password or PIN to log in.<br />
<br />
== Wifi ==<br />
<br />
=== Wifi disappears ===<br />
<br />
If wifi stopped working, first try usual means:<br />
* switching wifi off and on again<br />
* reboot PineTab<br />
<br />
If it still doesn't work, open terminal and type this:<br />
<br />
nmcli r<br />
<br />
If output is two lines with red word '''disabled''' under word '''WIFI''' - rejoice, since this issue is known (although it's not yet investigated well enough to figure out when it happens, so clues to developers are likely welcome). To fix it, just type this in the terminal:<br />
<br />
nmcli r wifi on<br />
<br />
<br />
=== Wifi missing if started with keyboard attached ===<br />
<br />
UT [OS version: RC#6 (2020-W37)]<br />
<br />
symptom: if you started with keyboard attached wifi will not come up<br />
<br />
reason: the service urfkill is not running<br />
<br />
fix:<br />
sudo service urfkill restart<br />
<br />
=== Wifi radio reception is very weak ('''tweak needed''') ===<br />
<br />
This needs a tweak! How to open the PineTab?<br />
<br />
Tested with UT, Mobian and Archlinux: sitting right beside the router gives a connection (ca. 60% level). No reception in a distance of 7 meters, no wall, just an opened door, some edges, router not directly visible. Pinephone right beside the Pinetab has an absolutly stable wifi connection.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineTab/Early-Adopter&diff=7117PineTab/Early-Adopter2020-09-15T18:57:15Z<p>UniversalSuperBox: </p>
<hr />
<div>The PineTab Early Adopter edition was the first hardware revision of the PineTab which shipped to customers. Shipping began on September 6, 2020.<br />
<br />
== Software ==<br />
<br />
The device shipped with a beta build of Ubuntu Touch by UBports. This build is available to download at https://ci.ubports.com/job/rootfs/job/rootfs-pinetab-systemimage/18/. It has the following problems which are software, not hardware, issues:<br />
<br />
* The mouse fails to move around the entire screen. It is stuck in an 800px horizontal box.<br />
* It is not possible to enable Bluetooth<br />
* Cameras do not function<br />
* Portrait mode does not function<br />
* The external keyboard is not always detected<br />
* There is a faint crackling noise on startup<br />
* Pasting an item on File Manager after Copy/Cut reboots the operating system<br />
* GUI apps with Libertine are not working, because of missing bits between wayland and Libertine<br />
<br />
The first-time setup wizard advises the user to unplug the keyboard dock (avoiding the mouse issues) and update the system. Unfortunately, as of this update to this page (September 8, 2020) this will not fix any of the issues above.<br />
<br />
=== 16GB/64GB storage software error ===<br />
<br />
The image installed on the device was sized for a 16GB (~14GiB) eMMC, but the PineTab shipped with a 64GB (~58GiB) eMMC chip installed. This means that the "Storage" page in the "About" section of Ubuntu Touch System Settings will show total storage as 14.0GiB until the partition table on the device is edited. <br />
<br />
UBports developers are currently working on a solution that will automatically edit the partition table and resize the data partition without disturbing any user data.<br />
<br />
=== Installing using apt ===<br />
<br />
Installing software on the read-only root filesystem is unsupported on Ubuntu Touch. You should be able to find updates in System Settings -> Updates and new applications in the OpenStore. If you would like to install and use terminal software from the Ubuntu repositories, see [https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html Run desktop applications in the UBports Documentation] to set up a Libertine container. Unfortunately, graphical software does not yet work through Libertine. This issue is tracked as [https://github.com/ubports/libertine/issues/68 ubports/libertine#68]<br />
<br />
=== Enabling ssh ===<br />
Naturally, you should be wary of enabling ssh for security reasons but everything is there. Almost.<br />
<br />
Edit /etc/ssh/sshd_config<br />
<br />
Change the following:<br />
* PasswordAuthentication yes<br />
* ChallengeResponseAuthentication yes<br />
<br />
Then:<br />
/etc/init.d/sshd start<br />
<br />
Use user phablet along with your password or PIN to log in.<br />
<br />
== Wifi ==<br />
<br />
=== Wifi disappears ===<br />
<br />
If wifi stopped working, first try usual means:<br />
* switching wifi off and on again<br />
* reboot PineTab<br />
<br />
If it still doesn't work, open terminal and type this:<br />
<br />
nmcli r<br />
<br />
If output is two lines with red word '''disabled''' under word '''WIFI''' - rejoice, since this issue is known (although it's not yet investigated well enough to figure out when it happens, so clues to developers are likely welcome). To fix it, just type this in the terminal:<br />
<br />
nmcli r wifi on<br />
<br />
<br />
=== Wifi missing if started with keyboard attached ===<br />
<br />
UT [OS version: RC#6 (2020-W37)]<br />
<br />
symptom: if you started with keyboard attached wifi will not come up<br />
<br />
reason: the service urfkill is not running<br />
<br />
fix:<br />
sudo service urfkill restart<br />
<br />
=== Wifi radio reception is very weak ('''tweak needed''') ===<br />
<br />
This needs a tweak! How to open the PineTab?<br />
<br />
Tested with UT, Mobian and Archlinux: sitting right beside the router gives a connection (ca. 60% level). No reception in a distance of 7 meters, no wall, just an opened door, some edges, router not directly visible. Pinephone right beside the Pinetab has an absolutly stable wifi connection.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineTab/Early-Adopter&diff=6923PineTab/Early-Adopter2020-09-08T17:20:33Z<p>UniversalSuperBox: </p>
<hr />
<div>The PineTab Early Adopter edition was the first hardware revision of the PineTab which shipped to customers. Shipping began on September 6, 2020.<br />
<br />
== Software ==<br />
<br />
The device shipped with a beta build of Ubuntu Touch by UBports. This build is available to download at https://ci.ubports.com/job/rootfs/job/rootfs-pinetab-systemimage/18/. It has the following problems which are software, not hardware, issues:<br />
<br />
* The mouse fails to move around the entire screen. It is stuck in an 800px horizontal box.<br />
* It is not possible to enable Bluetooth<br />
* Cameras do not function<br />
<br />
The first-time setup wizard advises the user to unplug the keyboard dock (avoiding the mouse issues) and update the system. Unfortunately, as of this update to this page (September 8, 2020) this will not fix any of the issues above.<br />
<br />
=== 16GB/64GB storage software error ===<br />
<br />
The image installed on the device was sized for a 16GB (~14GiB) eMMC, but the PineTab shipped with a 64GB (~58GiB) eMMC chip installed. This means that the "Storage" page in the "About" section of Ubuntu Touch System Settings will show total storage as 14.0GiB until the partition table on the device is edited. <br />
<br />
UBports developers are currently working on a solution that will automatically edit the partition table and resize the data partition without disturbing any user data.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineTab/Early-Adopter&diff=6865PineTab/Early-Adopter2020-09-07T20:50:58Z<p>UniversalSuperBox: </p>
<hr />
<div>The PineTab Early Adopter edition was the first hardware revision of the PineTab which shipped to customers. Shipping began on September 6, 2020.<br />
<br />
== Software ==<br />
<br />
The device shipped with a beta build of Ubuntu Touch by UBports. This build is available to download at https://ci.ubports.com/job/rootfs/job/rootfs-pinetab-systemimage/18/. It has the following problems which are software, not hardware, issues:<br />
<br />
* The mouse fails to move around the entire screen. It is stuck in an 800px horizontal box.<br />
* It is not possible to enable Bluetooth<br />
* Cameras do not function<br />
<br />
The first-time setup wizard advises the user to unplug the keyboard dock (avoiding the mouse issues) and update the system. Unfortunately, as of this update to this page (September 7, 2020) this will not fix any of the issues above.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PineTab/Early-Adopter&diff=6233PineTab/Early-Adopter2020-07-19T20:34:47Z<p>UniversalSuperBox: Created page with "This page is a placeholder that is noted on the small "getting started" leaflet included with the PineTab "Early Adopter" batch. It is meant to include information to help new..."</p>
<hr />
<div>This page is a placeholder that is noted on the small "getting started" leaflet included with the PineTab "Early Adopter" batch. It is meant to include information to help new PineTab users get oriented with their device, its features, and any steps they need to take right away upon receiving the device.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PinePhone_Software_Releases&diff=5555PinePhone Software Releases2020-05-11T21:40:24Z<p>UniversalSuperBox: Edit Ubuntu Touch download location</p>
<hr />
<div><br />
This page is intended to help you install a software release on your [[PinePhone]]. It also provides details about all available releases as well as links to further resources.<br />
<br />
= General instructions =<br />
<br />
Releases are first installed to a Micro SD card. Choose a card with fast I/O (of small files) for the best performance. See [[#Other Resources]] for performance tests of various SD cards.<br />
<br />
This section has generic installation instructions. Please see the [[#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 />
== Preparation of SD card ==<br />
# Download your chosen image from the options below<br />
# Extract the compressed file<br />
# Write the image to your SD card<br />
# Plug SD card into phone<br />
# Boot phone<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]] then return to this page.<br />
<br />
USING BMAPTOOL<br />
Download the .img.xz and the .img.bmap files.<br />
Run $ bmaptool copy --bmap image.bmap image.xz /dev/sdX<br />
This takes 2.5mins to flash a 4Gb file.<br />
<br />
== Installation to eMMC (Optional) ==<br />
<br />
=== Method Using Factory Installed Tools ===<br />
<br />
The initial OS you get with your phone has the option to flash an image on SD card to eMMC. <br />
<br />
# Copy (not flash) the image file to a formatted SD card.<br />
# Insert SD card into powered-off phone.<br />
# Turn on phone and select option to install to eMMC.<br />
<br />
=== Safe & Easy Method ===<br />
<br />
[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]<br />
<br />
# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]<br />
# flash the Jumpdrive image to a SD card<br />
# boot from the SD card<br />
# connect the PinePhone to your computer using USB-A -> USB-C cable.<br />
# flash the exposed (mounted) PinePhone drive with a chosen OS image as you'd flash any SD card, and resize partitions (optional, see below)<br />
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card<br />
# boot into your OS of choice on 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.<br />
<br />
=== Safe With No Extra Tools, But Slower ===<br />
<br />
# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)<br />
# Insert SD card and boot the phone<br />
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file. <br />
# Build the OS (Optional)<br />
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=/dev/mmcblkX of=/dev/mmcblkY bs=1M</code> where X is the number label of the SD card, and Y is the number label of the eMMC. 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. Then, resize partition to fill up entire disk (see below).<br />
# Turn off phone, remove SD card. Turn on phone.<br />
<br />
=== Risky Method ===<br />
<br />
Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.<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 />
== Resize partition to fit disk space ==<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.<br />
<br />
Using Growpart: <br />
<br />
growpart /dev/sdX 1 <br />
resize2fs /dev/sdX 1<br />
<br />
Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) 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 lsblk).<br />
<br />
If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.<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. <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/mmcblk0 bs=8k seek=1 count=4<br />
will clear the relevant sectors of your card. <br />
<br />
== Backlight ==<br />
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 />
Sailfish is one OS that initially uses automatic backlight control and the default setting makes the screen appear blank. When shining a bright light on the screen, you can still navigate the screen (and maybe the screen switches on temporarily due to the light sensor). This will make it possible for you to disable auto brightness in Settings, Display.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Software Releases =<br />
This is a list of OSs that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used. From Linux kernel V5.7 most drivers are included.<br />
<br />
== postmarketOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and phosh. <br />
<br />
* ''' Download location '''<br />
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you. See for example [https://forum.pine64.org/showthread.php?tid=8285 this forum thread.] <br />
<br />
Note pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC.]<br />
<br />
[http://images.postmarketos.org/pinephone/ Demo images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own user-id and password. '''NOTE: The Phosh lock screen requires your password, but only presents a numeric keyboard. So you should use [[only]] numbers in your password.''')<br />
<br />
* ''' What works, what does not work '''<br />
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]<br />
<br />
If you install firefox browser (or are using a demo image that already has it installed) [https://wiki.postmarketos.org/wiki/Firefox then these hints in the pmOS wiki are recommended.] GDK_SCALE=1 is best for PinePhone screen, enable Wayland gets application to fit screen and allow keyboard entry.<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker for PinePhone support]<br />
<br />
* ''' Contributions '''<br />
[https://wiki.postmarketos.org/wiki/Contributing See postmarketOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Ubuntu Touch by UBports ==<br />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.<br />
<br />
A short, state-of-the-art (as at 2 April 2020) [https://youtu.be/3Ne6G0-hn9g demo on YouTube.]<br />
<br />
[https://ubuntu-touch.io/ 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 img and flash to your pinephone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.<br />
<br />
* ''' Download location '''<br />
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]<br />
<br />
* ''' user-id/password '''<br />
Set up during boot<br />
<br />
* ''' What works, what does not work '''<br />
[https://gitlab.com/ubports/community-ports/pinephone Scroll down to the bottom of this page.]<br />
<br />
* ''' Where/how to report defects '''<br />
[https://gitlab.com/ubports/community-ports/pinephone See UBports gitlab page.]<br />
<br />
* ''' Contributions '''<br />
[https://ubports.com/foundation/sponsors See UBports website for how to donate.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Debian-PinePhone ==<br />
[[File:Debian-logo.png]]<br />
<br />
See [https://forum.pine64.org/showthread.php?tid=9016 this thread in the forum.]<br />
<br />
An unofficial Debian build for ARM64 running with the [https://developer.puri.sm/Librem5/Software_Reference/Environments/Phosh.html phosh user interface] (developed by Purism, phosh uses [https://en.wikipedia.org/wiki/Wayland_(display_server_protocol) Wayland] instead of [https://en.wikipedia.org/wiki/X.Org_Server 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, of course). Current version is Debian Bullseye. <br />
<br />
* ''' Download location '''<br />
[http://pinephone.a-wai.com/images/ Debian-pinephone downloadable images]<br />
<br />
Don't forget to extract the image before installing: <br />
$ gzip -d Downloads/debian-pinephone-*.img.gz<br />
<br />
See the [https://gitlab.com/a-wai/debos-pinephone project page] for specific installation instructions.<br />
<br />
* ''' user-id/password '''<br />
debian/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
See [https://gitlab.com/a-wai/debos-pinephone/-/blob/master/README.md the project's README file] for most up to date status.<br />
<br />
Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].<br />
<br />
* ''' Where/how to report defects '''<br />
It is recommended that you log your bug reports in [https://gitlab.com/a-wai/debos-pinephone/issues/ the project's issue tracker.] As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Debian-PinePhone 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.<br />
<br />
* ''' Contributions '''<br />
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/a-wai/debos-pinephone/ Gitlab.]<br />
<br />
=== User Experience Notes ===<br />
If not already mentioned on the project page, the [https://forum.pine64.org/showthread.php?tid=9016 thread] might have known workarounds to software and user experience issues as contributed by the users.<br />
<br />
==== Most of Debian's repository is available ====<br />
There are packages that apt won't find, which need to be cross compiled ("ported") to ARM64 (see [https://wiki.debian.org/Arm64Port Debian's wiki on ARM64 port]), but the process is fairly easy. Most developers package their software for the AMD64 version of Debian, so they will throw an error when run; if you have the source code, you can compile it to run on ARM64/PinePhone. If you do so, you should contact the developers so they can provide precompiled ARM64 packages for others in the future. You should also contact Debian if you have working ARM64 packages not listed on [https://wiki.debian.org/Arm64Port this page], since this helps them track the status of ARM64 with Debian. Give their wiki page some TLC.<br />
<br />
==== Apps that don't work with Wayland ==== <br />
If you encounter an app that only works with X11 and not Wayland, report it upstream to the app's developers.<br />
<br />
==== The Chatty app ==== <br />
Requires that in order to start a new text, you need to enter +[country code]-[phone number]. Without the + and the country code (+1 for USA) you won't be able to send a new text.<br />
<br />
==== To use the USB port for networking ==== <br />
Or for serial port access you should<br />
sudo apt install pinephone-devtools<br />
Note this also installs openssh-server.<br />
[https://forum.pine64.org/showthread.php?tid=9016&pid=64038&highlight=%22pinephone-devtools%22#pid64038 See this post.]<br />
<br />
==== To enable WiFi hotspot ====<br />
sudo apt install dnsmasq-base<br />
Then you need to configure a suitable range of available IP addresses in /etc/dnsmasq.conf e.g. the following single line:<br />
dhcp-range=10.42.0.50,10.42.0.150,24h<br />
Finally in Settings, WiFi, enable your hotspot.<br />
<br />
==== To adjust screen resolution ==== <br />
References: [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/] [https://forum.pine64.org/showthread.php?tid=9016&pid=61403#pid61403] [https://forum.pine64.org/showthread.php?tid=9016&pid=61685#pid61685]<br />
sudo apt install linux-libc-dev build-essential ninja-build meson cmake libwayland-dev yad<br />
Continue the rest of the instructions on [https://puri.sm/posts/easy-librem-5-app-development-scale-the-screen/ this page]<br />
When you finish, you will have a touch-capable app you can use to adjust resolution any time, useful when switching between various apps. <br />
Unlike other solutions, this works across reboots.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== SailfishOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.<br />
<br />
* ''' Download location '''<br />
The SailfishOS 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 our 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 />
* ''' user-id/password ''' Set PIN on initialization.<br />
<br />
* ''' What works, what does not work '''<br />
04 May 2020. The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (eg MTP file transfer now works) but there are several glitches, the most serious being total freeze requiring reboot. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.<br />
09 May 2020. Voice calls now work....(in pipeline, arriving in builds within days). If you have a Jolla registration a minor bug means you have to submit the request twice.<br />
<br />
If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a poor selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment. <br />
<br />
== Updates ==<br />
OTA is supported: `zypper refresh && zypper update` as root (`devel-su` 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 />
<br />
* ''' Where/how to report defects '''<br />
<br />
See [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues the Sailfish wiki] for links to their forum as well as info required when reporting an issue.<br />
<br />
* ''' Contributions '''<br />
[https://sailfishos.org/wiki/SailfishOS See the SailfishOS wiki for options to contribute.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== PureOS ==<br />
[[File:Pureos.png]]<br />
<br />
PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.<br />
<br />
* ''' Download location '''<br />
This is an unofficial/unsupported creation by ''mozzwald'' and maintained by clover that can be downloaded [http://pureos.ironrobin.net/droppy/#/Images here.] <br />
<br />
* ''' user-id/password '''<br />
purism/123456<br />
<br />
* ''' Build instructions '''<br />
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Fedora ==<br />
http://files.pine64.org/sw/pine64_installer/json/fedora.png<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 />
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]<br />
<br />
The images are compressed with zstd because the maintainer needs an excuse to use zstd.<br />
<br />
* ''' user-id/password '''<br />
pine/1111<br />
<br />
* ''' What works, what does not work '''<br />
* WiFi, Bluetooth, SMS, Data, Calls all work!<br />
* There are still a few bugs though, and [some features don't have driver support yet https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix] on any PinePhone distribution. <br />
<br />
* ''' Where/how to report defects '''<br />
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker.] Be sure to include logs if applicable!<br />
<br />
* ''' Contributions '''<br />
Please help! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Arch Linux ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
An (unofficial) barebone Arch Linux ARM image, all you have is just a shell and SSH.<br />
<br />
* ''' Download location '''<br />
https://github.com/dreemurrs-embedded/Pine64-Arch/releases<br />
<br />
* ''' user-id/password '''<br />
alarm/alarm<br />
<br />
* ''' What works, what does not work '''<br />
It's just fast and smooth, there's nothing, you'll have to install a desktop at your own. GNOME is a good example to look at.<br />
<br />
To access the device, ssh to 172.16.42.1 with the credentials above. <br />
<br />
* ''' Contributions '''<br />
Feel free to send us merge requests on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Manjaro ARM ==<br />
http://files.pine64.org/sw/pine64_installer/json/manjaro.png<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 />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro forum announcement of Alpha5 version]<br />
<br />
* ''' user-id/password '''<br />
** manjaro/1234<br />
** root/root<br />
<br />
* ''' What works, what does not work '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See Manjaro announcement.]<br />
<br />
In particular phone calls do NOT yet work from the Phone application.<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
[https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 See the end of the announcement here.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Maemo Leste ==<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<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 />
[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 />
* ''' user-id/password '''<br />
root/toor<br />
<br />
You may use "sudo" directly.<br />
<br />
* ''' What works, what does not work '''<br />
For current status and work arounds 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 their github, see below).<br />
<br />
* ''' Where to Report Issues '''<br />
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.<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]<br />
<br />
* ''' Development '''<br />
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 />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Nemo Mobile ==<br />
http://files.pine64.org/sw/pine64_installer/json/nemo_mobile.png<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
See the new website nemomobile.net/<br />
You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to sd card on the pinephone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).<br />
<br />
* ''' Download location '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Download location is here on GitHub.] The latest version here is not an .img and not for beginners!<br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
[https://github.com/neochapay/nemo-device-dont_be_evil/ Scroll down the page here.]<br />
<br />
* ''' Where/how to report defects '''<br />
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== KDE Neon ==<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
Based on KDE Neon for the desktop, comes with Plasma Mobile.<br />
<br />
* ''' Download location '''<br />
[https://images.plasma-mobile.org/pinephone/ Plasma mobile images can be found here.]<br />
<br />
* ''' user-id/password '''<br />
phablet/1234<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== NixOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
''NixOS support is handled through the Mobile NixOS project.''<br />
<br />
* [https://mobile.nixos.org/ Project home page]<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 Wi-Fi.<br />
<br />
<cite><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 />
</cite><br />
<br />
* ''' Where/how to report defects '''<br />
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a Pinephone when reporting issues.<br />
<br />
* ''' Contributions '''<br />
[https://nixos.org/nixos/community.html Details about contributions and donations are on the NixOS website.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== LuneOS ==<br />
http://files.pine64.org/sw/pine64_installer/json/luneos.jpg<br />
Based on WebOS by LG, comes with Luna Next desktop environment.<br />
<br />
* ''' Download location '''<br />
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]<br />
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage. <br />
<br />
* ''' user-id/password '''<br />
<br />
* ''' What works, what does not work '''<br />
<br />
* ''' Where/how to report defects '''<br />
<br />
* ''' Contributions '''<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Aurora ==<br />
Available soon? https://mobile.twitter.com/neochapay/status/1189552654898188288?p=p<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
== Android 10 ==<br />
https://www.pine64.org/wp-content/uploads/2020/03/androidpp.jpg<br />
<br />
While I didn't find a download link yet, I did find this image on the March community update from Pine64 of an Android 10 rom running on the Pinephone by [https://github.com/Icenowy Moe Icenowy]. This image is absolutely bare-bones (no applications yet) and comments on IRC indicated it was a theoretical test only, rather than a step towards a release.<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Installing Any ARM64 Distribution =<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 distro to the PinePhone.<br />
<br />
'''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 https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).<br />
<br />
# Create a boot (from 4MiB to about 252MiB) and root (from 252 MiB to the end of the card) filesystem on the SD card.<br />
# Format the boot partition with vfat, and the root partition with f2fs.<br />
# Extract the root filesystem from your distro's ARM image into the root filesystem on the sd card. Do not copy the partition, copy the files (in archive mode: like rsync -ar).<br />
# Edit /etc/fstab to match your partitions.<br />
# Grab megi's kernel from https://xff.cz/kernels/ (you probably want 5.6).<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 />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Mobile Carrier APN Settings =<br />
<br />
See thread: https://forum.pine64.org/showthread.php?tid=9150<br />
<br />
Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.<br />
<br />
''' Distributions with Phosh (Debian + Phosh, pmOS + Phosh, Fedora) '''<br />
<br />
APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (pureOS, Debian + Phosh) or <code>Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).<br />
<br />
== ATT-based (USA) ==<br />
<br />
* ATT<br />
* Metro<br />
* <br />
<br />
== Red Pocket (USA) ==<br />
<br />
You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.<br />
<br />
APN settings:<br />
<br />
name: Red Pocket<br />
APN: RESELLER<br />
<br />
== Mint Mobile (USA) ==<br />
<br />
Source: https://www.mintmobile.com/setup-for-android/<br />
<br />
Use the following APN settings:<br />
<br />
Name: Ultra<br />
APN: Wholesale<br />
<br />
Call their customer service to activate using the number on their website, or activate on their website: https://my.mintmobile.com/activation. You may also need to reboot your phone.<br />
<br />
== Tracfone (USA?) == <br />
<br />
'''BYOP SIM Card Kit''': works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit<br />
<br />
Calls, SMS, and 3G/4G data known to work with AT&T SIM. (most likely works for T-Mobile as well)<br />
<br />
Use the following APN settings:<br />
<br />
Name: Tracfone<br />
APN: RESELLER<br />
<br />
== Mobile Vikings (Belgium) ==<br />
<br />
Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-<br />
<br />
Name: Mobile Vikings<br />
APN: web.be<br />
Username: web<br />
Password: web<br />
<br />
== Virgin Mobile (Canada) ==<br />
<br />
Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.<br />
<br />
Name: Mobile Fast Web<br />
APN: pda2.bell.ca<br />
Username:<br />
Password:<br />
<br />
== Carriers That Do Not Work ==<br />
<br />
* FreedomPop (USA): VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to fp.com.attz. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit. <br />
* VoLTE services like Sprint or Verizon<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div><br />
<br />
= Other Resources =<br />
Community<br />
* [https://forum.pine64.org/forumdisplay.php?fid=120 PinePhone Forum]<br />
* [http://www.pine64.xyz:9090/?channels=PINEPHONE PinePhone IRC Channel]<br />
<br />
Hardware information<br />
* [[PinePhone]] hardware details in this Pine64 wiki.<br />
* [[PinePhone_v1.1_-_Braveheart]] hardware details specific to the Braveheart handsets.<br />
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here,] and the preceeding 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 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://store.pine64.org/?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 micro SD cards.]<br />
<br />
<div class="center" style="background-color: lightyellow;">[[#top | '''Return to top of page''']]</div></div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PinePhone_v1.1_-_Braveheart&diff=4259PinePhone v1.1 - Braveheart2019-12-16T21:05:41Z<p>UniversalSuperBox: Created page with "The PinePhone v1.1 "Braveheart" is a hardware revision of the PinePhone due to ship in January 2020. This page contains resources which are exclusive to the 1.1 revision of t..."</p>
<hr />
<div>The PinePhone v1.1 "Braveheart" is a hardware revision of the PinePhone due to ship in January 2020.<br />
<br />
This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see [[PinePhone]].<br />
<br />
== Schematic ==<br />
<br />
[http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf Hardware schematic]<br />
<br />
== Changes from 1.0 ==<br />
<br />
Braveheart is slightly different from the 1.0 revision of the Pinephone. These differences should not require creating different images.<br />
<br />
# Added CPU shielding and cover plate<br />
# Swap PC3 to FLASH_EN and PD24 to FLASH_TRIGOUT, where previously they were reversed<br />
# Add pulldown resistor on PD24 (FLASH_TRIGOUT) so the flash LED does not light on boot<br />
# Connect WiFi enable to VD33<br />
# Set the EG25G's PWRKEY on by default (see resistor R1526)<br />
# Add R630 resistor location, populate with 0K by default. Allows adjusting to different battery thermistors in case this is not possible in software.<br />
# Add voltage shift to Pogo pins I2C-CLK, I2C-DATA, and INT. The Pogo Pin specified voltage is 3.3v while the A64's I2C is 2.8V.<br />
<br />
== Known issues ==<br />
<br />
This section lists problems known on the 1.1 revision hardware, possibly because they carried over from the 1.0 revision.<br />
<br />
=== Modem Ring Indicator placement is not ideal ===<br />
<br />
The EG25G's Ring Indicator pin is currently routed to GPIO pin PB2.<br />
<br />
Ring Indicator is a configurable signaling pin capable of notifying the modem's host of incoming messages or calls. This makes it important to read the status of the pin during (ARISC / Super Standby) sleep, since incoming calls or text messages must wake the device.<br />
<br />
Using the PB bank of GPIO on the A64 requires VCC-IO to be switched on. The only bank that does not have this requirement is the PL bank, at least as far as we can tell. Using information from the (related) A83T's manual:<br />
<br />
"In the super standby mode,GPIO B/C/D/E/F/G/H of VDD_SYS domain can hold a particular output state through GPIO pad hold function,but VCC power of GPIO can not be closed at this time"<br />
<br />
Ideally, Ring Indicator would be routed to somewhere on the PL bank because it stays active even when VCC-IO is switched off. In the current form, VCC-IO must stay on in Super Standby to allow the use of the Ring Indicator. The power usage difference between VCC-IO off and on is currently unknown, however, since [https://github.com/crust-firmware/crust crust] is not able to disable peripherals or clock trees.<br />
<br />
Re-routing Ring Indicator would require a new Device Tree for the system, so different images may need to be created.</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PinePhone&diff=4258PinePhone2019-12-16T21:05:30Z<p>UniversalSuperBox: Get the capitalization of PinePhone right -_-</p>
<hr />
<div>The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. A "braveheart" edition is currently available for purchase from the PINE64 store, though it should be noted that this version comes without a preinstalled OS, and is geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.<br />
<br />
== Specifications ==<br />
<br />
'''Dimensions:''' 160.5 x 76.6 x 9.2mm <br><br />
'''Weight:''' Between 180-200 grams <br><br />
'''Build:''' Plastic <br><br />
'''SIM Card:''' Micro-SIM <br><br />
'''Display:'''<br />
: '''Size:''' 5.95 inches (151mm) diagonal<br />
: '''Type:''' HD IPS capacitive touchscreen, 16M colors<br />
: '''Resolution:''' 1440x720, 18:9 ratio <br><br />
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] <br><br />
'''RAM:''' 2GB LPDDR3 SDRAM <br><br />
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC <br><br />
'''Back Camera:''' Single 5MP, 1/4", LED Flash <br><br />
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" <br><br />
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) <br><br />
'''Communication: [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf EG25-G]'''<br />
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41<br />
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19<br />
: '''GSM:''' 850, 900, 1800, 1900 (MHz)<br />
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
: '''Bluetooth:''' 4.0, A2DP<br />
: '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass <br><br />
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras <br><br />
'''Battery:''' 2750-3000 mAh [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf Lithium ion] (replaceable with any Samsung J7 form-factor battery) <br><br />
'''I/O:''' USB Type-C (SlimPort), USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Hardware Revisions ==<br />
<br />
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]<br />
# PinePhone v1.0 - Developer batch<br />
# [[PinePhone v1.1 - Braveheart]]<br />
<br />
== Hardware Addons ==<br />
<br />
The PinePhone has 6 "pogo pins" on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3v power source, and an I2C interface.<br />
<br />
A step file for the back cover is [https://app.box.com/s/g1n9cvg60cg66utdhs7m5my1ftvd0jj8 freely available] for creating custom cases that interface with the pogo pins.<br />
<br />
== Killswitch configuration ==<br />
<br />
The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their on position is toward the top of the phone.<br />
<br />
[[File:PinePhone-main-board.jpg|600px|thumb|centre|Photo of Developer mainboard courtesy of Martijn Braam, postmarketOS]]<br />
<br />
# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.<br />
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.<br />
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.<br />
# Rear camera: On enables the rear camera, off disables.<br />
# Front camera: On enables the front camera, off disables.<br />
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.<br />
<br />
== Modem and Carrier Support ==<br />
<br />
To check if the PinePhone is supported on your carrier: <br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed under the [[#Specifications|specifications]] section).<br />
<br />
It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.<br />
<br />
== Operating Systems ==<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for phones:<br />
* [[#postmarketOS|postmarketOS]]<br />
* [[#Ubuntu Touch|Ubuntu Touch]]<br />
* [[#Sailfish OS|Sailfish OS]]<br />
* [[#Maemo Leste|Maemo Leste]]<br />
* [[#LuneOS|LuneOS]]<br />
<br />
=== postmarketOS ===<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinephone/ images page] to be flashed to the PinePhone.<br />
<br />
More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) dedicated PinePhone wiki page].<br />
<br />
=== Ubuntu Touch ===<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. The default password is <code>phablet</code>. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool. <br />
<br />
=== Sailfish OS ===<br />
The latest Sailfish OS 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, 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 />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions.<br />
<br />
=== Nemo Mobile ===<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
* For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
* DD image for 8GB micoSD card /16GB eMMC module and above:<br />
** [http://files.pine64.org/os/PinePhone/NemoMobile/nemo-pine64-release2019.11.tar.bz2 Release build 0.3 direct download from pine64.org]<br />
** MD5 (XZ file): CA25F72A97CEE57C1479B90F445F4A4B<br />
** size: 325MB<br />
<br />
=== Maemo Leste ===<br />
[https://maemo-leste.github.io/ Maemo Leste] images can be downloaded [https://maedevu.maemo.org/images/pinephone-dontbeevil/ here]. The default username is <code>root</code> and the password is <code>toor</code><br />
<br />
=== LuneOS ===<br />
[https://www.webos-ports.org/wiki/Main_Page LuneOS] downloads are available [http://build.webos-ports.org/luneos-testing/images/pinephone/ here].</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PinePhone&diff=4256PinePhone2019-12-16T20:23:14Z<p>UniversalSuperBox: Create link to 1.1 braveheart page, make other hardware revision entries read better</p>
<hr />
<div>The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. A "braveheart" edition is currently available for purchase from the PINE64 store, though it should be noted that this version comes without a preinstalled OS, and is geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.<br />
<br />
== Specifications ==<br />
<br />
'''Dimensions:''' 160.5 x 76.6 x 9.2mm <br><br />
'''Weight:''' Between 180-200 grams <br><br />
'''Build:''' Plastic <br><br />
'''SIM Card:''' Micro-SIM <br><br />
'''Display:'''<br />
: '''Size:''' 5.95 inches (151mm) diagonal<br />
: '''Type:''' HD IPS capacitive touchscreen, 16M colors<br />
: '''Resolution:''' 1440x720, 18:9 ratio <br><br />
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] <br><br />
'''RAM:''' 2GB LPDDR3 SDRAM <br><br />
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC <br><br />
'''Back Camera:''' Single 5MP, 1/4", LED Flash <br><br />
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" <br><br />
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) <br><br />
'''Communication: [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf EG25-G]'''<br />
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41<br />
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19<br />
: '''GSM:''' 850, 900, 1800, 1900 (MHz)<br />
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
: '''Bluetooth:''' 4.0, A2DP<br />
: '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass <br><br />
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras <br><br />
'''Battery:''' 2750-3000 mAh [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf Lithium ion] (replaceable with any Samsung J7 form-factor battery) <br><br />
'''I/O:''' USB Type-C (SlimPort), USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Hardware Revisions ==<br />
<br />
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]<br />
# Pinephone v1.0 - Developer batch<br />
# [[Pinephone v1.1 - Braveheart]]<br />
<br />
== Hardware Addons ==<br />
<br />
The PinePhone has 6 "pogo pins" on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3v power source, and an I2C interface.<br />
<br />
A step file for the back cover is [https://app.box.com/s/g1n9cvg60cg66utdhs7m5my1ftvd0jj8 freely available] for creating custom cases that interface with the pogo pins.<br />
<br />
== Killswitch configuration ==<br />
<br />
The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their on position is toward the top of the phone.<br />
<br />
[[File:PinePhone-main-board.jpg|600px|thumb|centre|Photo of Developer mainboard courtesy of Martijn Braam, postmarketOS]]<br />
<br />
# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.<br />
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.<br />
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.<br />
# Rear camera: On enables the rear camera, off disables.<br />
# Front camera: On enables the front camera, off disables.<br />
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.<br />
<br />
== Modem and Carrier Support ==<br />
<br />
To check if the PinePhone is supported on your carrier: <br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed under the [[#Specifications|specifications]] section).<br />
<br />
It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.<br />
<br />
== Operating Systems ==<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for phones:<br />
* [[#postmarketOS|postmarketOS]]<br />
* [[#Ubuntu Touch|Ubuntu Touch]]<br />
* [[#Sailfish OS|Sailfish OS]]<br />
* [[#Maemo Leste|Maemo Leste]]<br />
* [[#LuneOS|LuneOS]]<br />
<br />
=== postmarketOS ===<br />
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinephone/ images page] to be flashed to the PinePhone.<br />
<br />
More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) dedicated PinePhone wiki page].<br />
<br />
=== Ubuntu Touch ===<br />
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. The default password is <code>phablet</code>. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool. <br />
<br />
=== Sailfish OS ===<br />
The latest Sailfish OS 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, 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 />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions.<br />
<br />
=== Nemo Mobile ===<br />
Nemo Mobile is the open source build of Sailfish OS.<br />
<br />
* For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]<br />
* DD image for 8GB micoSD card /16GB eMMC module and above:<br />
** [http://files.pine64.org/os/PinePhone/NemoMobile/nemo-pine64-release2019.11.tar.bz2 Release build 0.3 direct download from pine64.org]<br />
** MD5 (XZ file): CA25F72A97CEE57C1479B90F445F4A4B<br />
** size: 325MB<br />
<br />
=== Maemo Leste ===<br />
[https://maemo-leste.github.io/ Maemo Leste] images can be downloaded [https://maedevu.maemo.org/images/pinephone-dontbeevil/ here]. The default username is <code>root</code> and the password is <code>toor</code><br />
<br />
=== LuneOS ===<br />
[https://www.webos-ports.org/wiki/Main_Page LuneOS] downloads are available [http://build.webos-ports.org/luneos-testing/images/pinephone/ here].</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PinePhone&diff=4025PinePhone2019-11-20T01:20:04Z<p>UniversalSuperBox: Remove dots after ordered lists</p>
<hr />
<div>The PinePhone is a smartphone platform created by the Pine64 community and supported by many partner projects. It should be available for five years from its consumer launch date, which is expected to occur in March 2020.<br />
<br />
== Specifications ==<br />
<br />
* BODY:<br />
** Dimensions: 160.5mm x 76.6mm x 9.2mm<br />
** Weight: Between 180-200 gram<br />
** Build: Plastic<br />
** SIM: Micro-SIM<br />
<br />
* DISPLAY:<br />
** Type: HD IPS capacitive touchscreen, 16M colors<br />
** Size: 5.95 inches<br />
** Resolution: 1440x720 pixels, 18:9 ratio<br />
<br />
* PLATFORM:<br />
** OS: Various open source mainline Linux or BSD mobile OSes <br />
** Chipset: Allwinner A64<br />
** CPU: Quad-core 1.2 GHz ARM Cortex A-53<br />
** GPU: MALI-400<br />
<br />
* MEMORY:<br />
** Internal: 16GB eMMC, 2GB LPDDR3 SDRAM<br />
** Expansion: micro SD Card support SDHC and SDXC<br />
<br />
* CAMERA:<br />
** Main Camera: Single 5MP, 1/4", LED Flash<br />
** Selfie Camera: Single 2MP, f/2.8, 1/5"<br />
<br />
* SOUND:<br />
** Loudspeaker: Yes<br />
** 3.5mm jack with mic: Yes<br />
<br />
* COMMUNICATION:<br />
** LTE-FDD: B1/ B2/ B3/ B4/ B5/ B7/ B8/ B12/ B13/ B18/ B19/ B20/ B25/ B26/ B28<br />
** LTE-TDD: B38/ B39/ B40/ B41<br />
** WCDMA: B1/ B2/ B4/ B5/ B6/ B8/ B19 <br />
** GSM: 850/900/1800/1900MHz<br />
** WLAN: Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
** Bluetooth: 4.0, A2DP<br />
** GPS: Yes, with A-GPS, GLONASS<br />
** NFC: No<br />
** FM Radio: No<br />
** USB: type C (SlimPort), USB Host, DisplayPort Alternate Mode output<br />
** 3.5mm jack doubles as hardware UART if killswitch 6 is deactivated<br />
<br />
* FEATURES:<br />
** Sensors: Accelerometer, gyro, proximity, ambient light, magnetometer(compass)<br />
** Actuator: Vibrator<br />
** Privacy Switches: Modem (disables cellular modem and GNSS/GPS), Wifi & Bluetooth, Microphone, and Cameras<br />
<br />
* BATTERY:<br />
** Removable Li-Po 2750-3000 mAh battery<br />
** Charging: USB Type-C, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
* PRICE:<br />
** USD $150 (16GB eMMC/2GB LPDDR3 SDRAM configuration)<br />
<br />
No other configurations of the PinePhone are available at this time.<br />
<br />
== History ==<br />
<br />
The PinePhone was announced at [https://archive.fosdem.org/2019/ FOSDEM 2019], February 2-4, 2019. The first [[Project Don't be evil]] devkit was on display at the Pine64 booth during the weekend.<br />
<br />
=== Hardware revisions ===<br />
<br />
The PinePhone platform went through two "developer kit" phases that partner projects used to prove their software on the upcoming platform.<br />
<br />
# [[Project Anakin]]<br />
# [[Project Don't be evil]]<br />
<br />
Additionally, two "early adopter" revisions of the platform were created:<br />
<br />
# [[PinePhone 1.0 "Developer"]]<br />
# [[PinePhone 1.1 "Brave Heart"]]<br />
<br />
The first generally available PinePhone batch was [[PinePhone 1.1 "Brave Heart"]]. Pre-orders for this batch started on November 15, 2019. It is expected to ship sometime in December 2019 to January 2020.<br />
<br />
A "full release" Pinephone, which will likely have board revision 1.2, will be released in 2020.<br />
<br />
== Killswitch configuration ==<br />
<br />
The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their on position is toward the top of the phone.<br />
<br />
# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.<br />
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.<br />
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.<br />
# Rear camera: On enables the rear camera, off disables.<br />
# Front camera: On enables the front camera, off disables.<br />
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.<br />
<br />
== PinePhone Concepture Photo ==<br />
[[File:PinePhone_concepture_drawing.jpg]]<br />
<br />
== PinePhone Case Photos ==<br />
[[File:PinePhone_Photo-4.jpg]]<br />
[[File:PinePhone_Photo-2.jpg]]<br />
[[File:PinePhone_Photo-3.jpg]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=PinePhone&diff=4024PinePhone2019-11-20T01:18:41Z<p>UniversalSuperBox: Rewrite page with the start of a beautiful new timeline</p>
<hr />
<div>The PinePhone is a smartphone platform created by the Pine64 community and supported by many partner projects. It should be available for five years from its consumer launch date, which is expected to occur in March 2020.<br />
<br />
== Specifications ==<br />
<br />
* BODY:<br />
** Dimensions: 160.5mm x 76.6mm x 9.2mm<br />
** Weight: Between 180-200 gram<br />
** Build: Plastic<br />
** SIM: Micro-SIM<br />
<br />
* DISPLAY:<br />
** Type: HD IPS capacitive touchscreen, 16M colors<br />
** Size: 5.95 inches<br />
** Resolution: 1440x720 pixels, 18:9 ratio<br />
<br />
* PLATFORM:<br />
** OS: Various open source mainline Linux or BSD mobile OSes <br />
** Chipset: Allwinner A64<br />
** CPU: Quad-core 1.2 GHz ARM Cortex A-53<br />
** GPU: MALI-400<br />
<br />
* MEMORY:<br />
** Internal: 16GB eMMC, 2GB LPDDR3 SDRAM<br />
** Expansion: micro SD Card support SDHC and SDXC<br />
<br />
* CAMERA:<br />
** Main Camera: Single 5MP, 1/4", LED Flash<br />
** Selfie Camera: Single 2MP, f/2.8, 1/5"<br />
<br />
* SOUND:<br />
** Loudspeaker: Yes<br />
** 3.5mm jack with mic: Yes<br />
<br />
* COMMUNICATION:<br />
** LTE-FDD: B1/ B2/ B3/ B4/ B5/ B7/ B8/ B12/ B13/ B18/ B19/ B20/ B25/ B26/ B28<br />
** LTE-TDD: B38/ B39/ B40/ B41<br />
** WCDMA: B1/ B2/ B4/ B5/ B6/ B8/ B19 <br />
** GSM: 850/900/1800/1900MHz<br />
** WLAN: Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
** Bluetooth: 4.0, A2DP<br />
** GPS: Yes, with A-GPS, GLONASS<br />
** NFC: No<br />
** FM Radio: No<br />
** USB: type C (SlimPort), USB Host, DisplayPort Alternate Mode output<br />
** 3.5mm jack doubles as hardware UART if killswitch 6 is deactivated<br />
<br />
* FEATURES:<br />
** Sensors: Accelerometer, gyro, proximity, ambient light, magnetometer(compass)<br />
** Actuator: Vibrator<br />
** Privacy Switches: Modem (disables cellular modem and GNSS/GPS), Wifi & Bluetooth, Microphone, and Cameras<br />
<br />
* BATTERY:<br />
** Removable Li-Po 2750-3000 mAh battery<br />
** Charging: USB Type-C, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
* PRICE:<br />
** USD $150 (16GB eMMC/2GB LPDDR3 SDRAM configuration)<br />
<br />
No other configurations of the PinePhone are available at this time.<br />
<br />
== History ==<br />
<br />
The PinePhone was announced at [https://archive.fosdem.org/2019/ FOSDEM 2019], February 2-4, 2019. The first [[Project Don't be evil]] devkit was on display at the Pine64 booth during the weekend.<br />
<br />
=== Hardware revisions ===<br />
<br />
The PinePhone platform went through two "developer kit" phases that partner projects used to prove their software on the upcoming platform.<br />
<br />
#. [[Project Anakin]]<br />
#. [[Project Don't be evil]]<br />
<br />
Additionally, two "early adopter" revisions of the platform were created:<br />
<br />
#. [[PinePhone 1.0 "Developer"]]<br />
#. [[PinePhone 1.1 "Brave Heart"]]<br />
<br />
The first generally available PinePhone batch was [[PinePhone 1.1 "Brave Heart"]]. Pre-orders for this batch started on November 15, 2019. It is expected to ship sometime in December 2019 to January 2020.<br />
<br />
A "full release" Pinephone, which will likely have board revision 1.2, will be released in 2020.<br />
<br />
== Killswitch configuration ==<br />
<br />
The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their on position is toward the top of the phone.<br />
<br />
#. Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.<br />
#. WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.<br />
#. Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.<br />
#. Rear camera: On enables the rear camera, off disables.<br />
#. Front camera: On enables the front camera, off disables.<br />
#. Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.<br />
<br />
== PinePhone Concepture Photo ==<br />
[[File:PinePhone_concepture_drawing.jpg]]<br />
<br />
== PinePhone Case Photos ==<br />
[[File:PinePhone_Photo-4.jpg]]<br />
[[File:PinePhone_Photo-2.jpg]]<br />
[[File:PinePhone_Photo-3.jpg]]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil&diff=3269Project Don't be evil2019-03-25T20:33:08Z<p>UniversalSuperBox: </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|500px|Image: 500 pixels]]<br />
[[Image:Qsud2Gt.jpg|500px|Image: 500 pixels]]<br />
<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 />
** [http://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.1.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Schematic]<br />
** [http://files.pine64.org/doc/PinePhone/Pinephone-devkit%20Board%20Structure.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Structure]<br />
* SOPine Module Schematic:<br />
** [http://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<br />
** [http://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 />
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]<br />
* [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]<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 />
* [http://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 />
* [http://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 />
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [http://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 />
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [http://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 />
*** [http://files.pine64.org/doc/datasheet/pinephone/GC20355Mp-module_for_pinephone_devkit.pdf 2MP CMOS Image Sensor Module Drawing]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/GC2035%20Product%20Brief.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Product Brief]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/GC2035%20DataSheet.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Datasheet]<br />
** 5MPixel Rear CMOS Camera module information:<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/ATK-OV5640-5Mp-module_for_pinephone_devkit.pdf 5MP CMOS Image Sensor Module Drawing]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OmniVision OV5460 5MP CMOS Image Sensor Datasheet]<br />
** LCD Touch Screen Panel information:<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" 1440x720 IPS LCD Panel Specification]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/JD9365D_DS_Preliminary_V0.01_20170427.pdf fiti JD9365D LCD Controller Datasheet]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" Front Panel Touch Screen Specification]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/FT6336GU_Upgrade_Spec_Ver1.0.pdf FocalTech FT6336GU Front Panel Touch Screen Specification]<br />
** Lithium Battery information:<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/ncr18650b.pdf Panasonic NCR18650B 3350mAH Lithium Ion Battery Specification]<br />
** Ethernet PHY information:<br />
*** [http://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 />
*** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** LTE module information:<br />
*** [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [http://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 />
*** [http://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 />
*** [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [http://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 />
*** [http://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 />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
<br />
== UBPorts mainline build ==<br />
* [https://ci.ubports.com/job/rootfs-pinephone/ UBPorts Jerkins for PinePhone]<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
<br />
== KDE Plasma Mobile build ==<br />
* Not Yet Ready *<br />
<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
== Postmarket OS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
<br />
== Sailfish OS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
== Maemo OS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
== NixOS build ==<br />
* Not Yet Ready *<br />
<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 =<br />
<br />
The single USB Type-C port defaults to "USB Host" (including when the device is off). The device will not charge when it is in USB Host mode.<br />
<br />
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 />
= Other Resources =<br />
* [http://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 />
* [http://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]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=File:Pinephone-1.1-flash-schematic.png&diff=3267File:Pinephone-1.1-flash-schematic.png2019-03-24T00:26:00Z<p>UniversalSuperBox: Schematic view of the Pinephone v1.1 (Don't be Evil) devkit's flash LED driver</p>
<hr />
<div>Schematic view of the Pinephone v1.1 (Don't be Evil) devkit's flash LED driver</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil&diff=3263Project Don't be evil2019-03-24T00:18:15Z<p>UniversalSuperBox: </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|500px|Image: 500 pixels]]<br />
[[Image:Qsud2Gt.jpg|500px|Image: 500 pixels]]<br />
<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 />
** [http://files.pine64.org/doc/PinePhone/Pinephone-devkit-SCH%20Ver%201.1.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Schematic]<br />
** [http://files.pine64.org/doc/PinePhone/Pinephone-devkit%20Board%20Structure.pdf "Don't Be Evil" PinePhone Dev kit Baseboard Structure]<br />
* SOPine Module Schematic:<br />
** [http://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<br />
** [http://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 />
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]<br />
* [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]<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 />
* [http://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 />
* [http://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 />
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [http://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 />
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [http://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 />
*** [http://files.pine64.org/doc/datasheet/pinephone/GC20355Mp-module_for_pinephone_devkit.pdf 2MP CMOS Image Sensor Module Drawing]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/GC2035%20Product%20Brief.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Product Brief]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/GC2035%20DataSheet.pdf GalaxyCore GC2035 2MP CMOS Image Sensor Datasheet]<br />
** 5MPixel Rear CMOS Camera module information:<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/ATK-OV5640-5Mp-module_for_pinephone_devkit.pdf 5MP CMOS Image Sensor Module Drawing]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OmniVision OV5460 5MP CMOS Image Sensor Datasheet]<br />
** LCD Touch Screen Panel information:<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" 1440x720 IPS LCD Panel Specification]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/JD9365D_DS_Preliminary_V0.01_20170427.pdf fiti JD9365D LCD Controller Datasheet]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/XBD572-IPS-HI010A%20SPEC.pdf 5.7" Front Panel Touch Screen Specification]<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/FT6336GU_Upgrade_Spec_Ver1.0.pdf FocalTech FT6336GU Front Panel Touch Screen Specification]<br />
** Lithium Battery information:<br />
*** [http://files.pine64.org/doc/datasheet/pinephone/ncr18650b.pdf Panasonic NCR18650B 3350mAH Lithium Ion Battery Specification]<br />
** Ethernet PHY information:<br />
*** [http://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 />
*** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** LTE module information:<br />
*** [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [http://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 />
*** [http://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 />
*** [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [http://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 />
*** [http://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 />
http://files.pine64.org/sw/pine64_installer/json/ubports.png<br />
<br />
== UBPorts mainline build ==<br />
* [https://ci.ubports.com/job/rootfs-pinephone/ UBPorts Jerkins for PinPhone]<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/plasma_mobile.png<br />
<br />
== KDE Plasma Mobile build ==<br />
* Not Yet Ready *<br />
<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/postmarketos.png<br />
<br />
== Postmarket OS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/sailfishos.png<br />
<br />
== Sailfish OS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/maemo_leste.png<br />
<br />
== Maemo OS build ==<br />
* Not Yet Ready *<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/nixos.png<br />
<br />
== NixOS build ==<br />
* Not Yet Ready *<br />
<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 =<br />
<br />
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 />
= Other Resources =<br />
* [http://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 />
* [http://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]</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=File:SOPINE-SPI-Flash.png&diff=3261File:SOPINE-SPI-Flash.png2019-03-24T00:07:05Z<p>UniversalSuperBox: Schematic of the SPI flash chip on the SOPINE module</p>
<hr />
<div>Schematic of the SPI flash chip on the SOPINE module</div>UniversalSuperBoxhttps://wiki.pine64.org/index.php?title=Project_Don%27t_be_evil&diff=3189Project Don't be evil2019-02-12T02:22:28Z<p>UniversalSuperBox: </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". It will be introduced at FOSDEM 2019 <br />
* Latly, the third phase which is the PinePhone itself - scheduled to be released in Q3 2019 (pending on software development).<br />
<br />
<br />
<br />
<br />
<br />
You can also flash an OS image manually; please follow the instructions below.<br />
<br />
= Software and OS Image Downloads =<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/archlinux.png<br />
<br />
== Arch Linux mainline build by anarsoul ==<br />
<br />
<br />
** [https://github.com/anarsoul/linux-build/releases/latest Direct download latest release build from anarsoul github and look for archlinux-xfce-sopine-xxxxxxxx-x.img.xz]<br />
* Login with<br />
** User Name: alarm, Password: alarm<br />
** User Name: root, Password: root<br />
* please login root and execute "pacman -Syu" for latest update<br />
* Standby feature not yet implemented<br />
<br />
<br />
http://files.pine64.org/sw/pine64_installer/json/aosc.png<br />
<br />
== AOSC Community mainline minimum build by icenowy ==<br />
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]<br />
** [https://github.com/AOSC-Dev/aosc-os-arm-bsps/tree/master/sunxi/u-boot-sun50i-a64-sopine-baseboard Icenowy's github for A64 SoC]<br />
* Login with<br />
** username: aosc<br />
** password: anthon<br />
<br />
<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 />
<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 />
* [http://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 />
* [http://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 />
= Project Don't be evil, SOPine Module and Baseboard Information, and Schematics =<br />
* Model "A" Baseoard Dimensions: 133mm x 80mm x 19mm<br />
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, USB type-C connector<br />
* [http://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]<br />
* [http://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]<br />
* SOPine Module Schematic:<br />
** [http://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]<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 />
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]<br />
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [http://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 />
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]<br />
* LPDDR3 information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 Datasheet]<br />
* eMMC information:<br />
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]<br />
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]<br />
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]<br />
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]<br />
** [http://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee eMMC Datasheet]<br />
* SPI NOR Flash information:<br />
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]<br />
** [http://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 />
** 5MPixel Rear CMOS Camera module information:<br />
*** [http://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]<br />
*** [http://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]<br />
*** [http://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]<br />
*** [http://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]<br />
** 5MPixel Rear CMOS Camera module information:<br />
** LCD Touch Screen Panel information:<br />
<br />
** Lithium Battery information:<br />
<br />
** Ethernet PHY information:<br />
*** [http://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64+ Board]<br />
*** [http://files.pine64.org/doc/datasheet/pine64/rtl8201cp.pdf Realtek RTL8201 10/100M Ethernet Transceiver for PINE A64 Board]<br />
** Wifi/BT module information:<br />
*** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]<br />
** LTE module information:<br />
*** [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]<br />
*** [http://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 />
*** [http://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 />
*** [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]<br />
*** [http://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 />
<br />
<br />
= Other Resources =<br />
* [http://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 />
* [http://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]</div>UniversalSuperBox