PINE64 - User contributions [en]

PineNote Development/UART

2024-12-31T08:56:37Z

Mweigand: Restructure the PineNote UART-dongle page: show stock uart picture and usage first and move the custom dongle section down

[[File:Pn_uart_connection.jpg|thumb|Batch 1+2 UART dongle in use]]

This page contains information on creating and using a [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle for the [[PineNote]].
The PineNote was shipped with a compatible UART dongle, but replacements are not available to order in case of loss or hardware fault.
Thankfully it is not difficult to make your own from easily-acquired components and a small bit of soldering.

Fear not if you've never soldered anything before!
This serves as an excellent first soldering project.
Borrow the tools from a friend, local hackerspace, or tool library.
Pine64 also makes [[Pinecil|a nice soldering iron]] themselves.

A PineNote UART dongle enables you to:
# Interact with the system boot menu
# Read system events in real time as the PineNote is used
# Fix the PineNote without opening the case if something goes wrong while [[PineNote Development/Flashing|flashing it]]

Since the PineNote is an embedded system, interfacing with it during boot is more complicated than with an ordinary computer.
The UART dongle enables you to do this.

The PineNote factory firmware runs UART at a baud rate of 1500000 bps, 8 data bits, 1 stop bit, no parity and no flow control.
The process by which the PineNote design was modified to include closed-case UART is documented [[PineNote/Hardware Changes/Closed Case UART|here]].

== Stock dongle ==
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}

The stock UART dongle included with the PineNote is a simple device that plugs directly into the PineNote's USB-C port. The dongle exposes a female USB-C port, which the user connects to their host computer to get access to the serial console UART. This design unfortunately ruled out passthrough USB connections, where the user connects to the PineNote via UART and USB simultaneously. The dongle is not currently available separately for purchase.

<gallery>
Pinenote-stock-uart-dongle-front.jpg|Front
Pinenote-stock-uart-dongle-back.jpg|Back
</gallery>

== Using the dongle ==

First, use your UART dongle to physically connect your PineNote to your computer:
# Plug the USB-UART adapter into one of your computer's USB ports
# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works

Once the hardware is connected, we need some program on your computer to communicate over that connection with 1500000 (1.5 million) bps, 8 data bits, 1 stop bit, no parity and no flow control.
Here's how you do that:
# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>
# Check your permissions; run <code>ls -l /dev/ttyUSB0</code> to see which groups have access to the dongle (probably <code>dialout</code> or <code>uucp</code>), and add your user to that group; remember you need to log out before group changes take effect
# Install [https://salsa.debian.org/minicom-team/minicom minicom] (or [https://askubuntu.com/q/40959 some other option], but the instructions below are written for <code>minicom</code>)
# In a terminal window, run <code>minicom -D /dev/ttyUSB0 -b 1500000</code> or run <code>minicom --setup</code> to specify these settings by default
# Alternatively, you can also <code>picocom</code> for the connection: <code>picocom --baud 1500000 --databits 8 --stopbits 1 --flow none --parity none /dev/ttyUSB0</code>
# Side note: If you are often using the UART dongle, it could make sense to define a shell alias for this:
<code>alias ppc='picocom --baud 1500000 --databits 8 --stopbits 1 --flow none --parity none /dev/ttyUSB0'</code>

Once the software is set up, power-cycle your PineNote; as the system boots you should see text appearing in your terminal window.
You can exit the session with <code>ctrl+a x</code> then pressing <code>Enter</code> to confirm.
Run <code>man minicom</code> for more details.

=== Sending commands (minicom) ===

Pressing <code>ctrl+a</code> in <code>minicom</code> enables you to send keystrokes to your PineNote.
The most important of these is <code>ctrl+c</code>, which if sent during boot will put you in the U-Boot command prompt.
You can then type <code>help</code> to list possible commands.

=== Troubleshooting Stock UART dongle ===

If you don't see any text in your terminal as the PineNote boots, or the text is garbled, try the following:

* Connect your USB-C breakout board to your PineNote in the opposite orientation
* Run <code>minicom</code> as sudo in case your user doesn't have appropriate permissions
* Ensure you are setting the baud rate to 1500000 (1.5 million), and (less importantly because these are probably used by default) 8 data bits, 1 stop bit, no parity and no flow control

If you can see text but are having trouble sending <code>ctrl+c</code> to the PineNote during boot:
* Be sure you're typing <code>ctrl+a</code> first, or whatever escape sequence your terminal emulator uses
* Send it right as the PineNote is booting, before the loading bar appears on screen

== Building a new UART dongle ==

[[File:Pinenote-uart-dongle.jpeg|thumb|Basic non-stock PineNote UART dongle]]

A typical self-built PineNote UART dongle design has the following components:
# A USB-C breakout board with a male connector exposing the 24 pins of the PineNote's USB-C port
# A USB-UART adapter, to plug into a USB port of the computer you'll use to interface with the PineNote
# [https://en.wikipedia.org/wiki/Jump_wire Jump wires] to connect specific breakout board pins to pins on the USB-UART adapter
# Two 1,000 Ohm through-hole resistors to splice into the jump wires
# Electrical tape or heat shrink to wrap connectors and prevent shorts

You will also need the following tools:
# Soldering iron with solder
# Wire cutters & strippers

The PineNote's internal UART system is documented in [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf this schematic].
The purpose of all 24 USB-C pins is documented [https://en.wikipedia.org/wiki/USB-C#Receptacles on the USB-C Wikipedia page].
We are interested in three sets of pins:
# The SBU1 (A8) and SBU2 (B8) side band use pins
# The CC1 (A5) and CC2 (B5) configuration channel pins
# The GND [https://en.wikipedia.org/wiki/Ground_(electricity) ground return] pins (A1, A12, B1, and B12)

In the PineNote UART schematic you can see (on the bottom right diagram labeled <code>USB_TYPEC_Male</code>) the side band pins are given the labels <code>UART2_TX_SUB1</code> for A8 and <code>UART2_RX_SUB2</code> for B8.
The first (TX) is used for transmitting data and the second (RX) is used for receiving data, from the perspective of the PineNote.
Also note the configuration channel pins labeled <code>TYPEC_CC1</code> for A5 and <code>TYPEC_CC2</code> for B5.
The diagram shows they must be connected to a 3.3V source in parallel, mediated by resistors.
Per the USB-C standard, when these pins are pulled high this indicates the device should enter [https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode Debug Accessory Mode]; connecting them to a voltage source & limiting the current with [https://www.electronics-tutorials.ws/logic/pull-up-resistor.html pull-up resistors] accomplishes this.
The schematic indicates 10,000 Ohm resistors, but community member Visti Andresen (talpadk) experimented and found 1,000 Ohm resistors work better.
Our mission is to wire up pins from a USB-UART adapter to a USB-C breakout board following these requirements.

=== Buying components ===

There are many possible USB-C breakout board designs available for purchase online.
One particularly useful design is a "passthrough" or "intercept" style, with both male and female USB-C ports.
This design is more versatile in case you want to reuse it in other projects, and also enables you to connect to the PineNote via UART and USB at the same time.
An example of this product can be found [https://pmdway.com/products/usb-3-1-type-c-male-to-female-breakout-test-board here], although you are encouraged to shop around for cheaper options.
If you're fine with a bit more soldering, there is a very cheap one [https://www.ebay.com/itm/275407037613 here].

Similarly, there are many USB-UART adapter designs available.
These devices plug into your computer and expose a number of pins themselves, connecting to specific pins on the breakout board with jump wires.
It is important to get a 3.3V model, or at least a model with the option of 3.3V, as a 5V source might fry the PineNote.
[https://pmdway.com/products/usb-to-ttl-serial-cp2104-6-pin-converter-module Here] is one example with jump wires included, although you are again encouraged to shop around for alternatives.

All other necessary components of our UART dongle are readily & cheaply available in many locations.

=== Splicing resistors ===

[[File:PineNote-UART-Y-pull-up-resistor-cable.jpg|thumb|The desired end result; wrap removed from resistors for illustration purposes.]]

This is the only difficult part of the whole process.
Your goal is to create a Y-shaped jump wire with 1,000 Ohm through-hole resistors spliced into each of the twin arms.
The solitary leg will connect to a 3.3V source on your USB-UART adapter.
The twin arms will connect to the configuration channel pins on your USB-C breakout board.
Per the USB-C standard, when these pins are pulled high this indicates the device should enter [https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode Debug Accessory Mode]; connecting them to a voltage source & limiting the current with [https://www.electronics-tutorials.ws/logic/pull-up-resistor.html pull-up resistors] accomplishes this.

For this project you'll need:
# A soldering iron with solder
# Wire cutters & strippers
# 2x jumper wires, male/female as compatible with your board designs
# 2x 1,000 Ohm through-hole resistors
# Electrical tape or heat shrink wrap

Consider buying extra jumper wires and resistors in case you mess up.
Also double-check that you have 1K resistors with [https://resistorcolorcodecalc.com/ this color code calculator].
Although the PineNote UART schematic says to use 10K Ohm resistors, community member Visti Andresen (talpadk) experimented and found 1K is more appropriate.
Assemble your Y-cable as follows:
# Graft one jump wire onto the other to form a Y shape using [https://www.youtube.com/watch?v=KpiEfuhPqew this] technique, ensuring solitary leg end is compatible with your USB-UART adapter
# Splice resistors into the twin arms using [https://www.youtube.com/watch?v=RMgMVqqjPZ0 this] technique
# Splice remaining jump wire onto the ends of the resistors, ensuring ends are compatible with your USB-C breakout board
# Cover all exposed wire & resistors with electrical tape or heat shrink wrap

=== Assembly ===

Once you have acquired all necessary components, assemble the UART dongle as follows:
# Connect a jump wire from the GND pin on the USB-UART adapter to any one of the four GND pins on the USB-C breakout board (A1, A12, B1, or B12)
# Connect a jump wire from the RXD pin on the USB-UART adapter to the <code>UART2_TX_SUB1</code> SBU1 pin on the USB-C breakout board (A8)
# Connect a jump wire from the TXD pin on the USB-UART adapter to the <code>UART2_RX_SUB2</code> SBU2 pin on the USB-C breakout board (B8)
# Connect your Y-shaped jump wire from the 3.3V source pin on the USB-UART adapter to the CC1 and CC2 pins on the USB-C breakout board (A5 and B5)
# Wrap all metal connectors in electrical tape or heat shrink to prevent accidental shorts

Be '''very certain''' of your connections for the 3.3V source and its cable, as there is a real risk of irreparably frying your PineNote if they're wrong!
Especially be sure you are connecting to a 3.3V source and not a 5V source.

Note that if you mix up the TX/RX pins, it will still work but the USB-C breakout board will just plug into the PineNote upside down.
You can therefore choose which orientation you want by swapping the TX/RX pin connections.
Experience shows that RX/TX-TX/RX connections will have the PineNote face down while connected, while RX/RX-TX/TX connections will put the PineNote face up.

=== Troubleshooting Custom UART dongles ===

If you don't see any text in your terminal as the PineNote boots, or the text is garbled, try the following:
* Ensure your GND, RX/TX, and CC jump wires are connected to the correct pins on both the USB-UART adapter and the USB-C breakout board

If you can see text but are having trouble sending <code>ctrl+c</code> to the PineNote during boot:
* Double-check your Y-shaped pull-up resistor cable; if this isn't working properly you'll probably be able to read text but not send text

== USB passthrough (only custom-built dongles) ==

If your USB-C breakout board has a passthrough/intercept design, you can connect to your PineNote over USB and UART at the same time.
This can be useful when you're doing development work on the PineNote boot process so you don't have to continually reconnect cables.
You'll need a USB-A to USB-C cable, connecting directly from your computer's USB-A hub to your USB-C breakout board's female USB-C port.
It's important to connect directly from USB-A, without any intermediate USB-C components.
Note that connecting a live USB cable to your USB-C breakout board in this way dramatically increases the danger of frying your PineNote with a short, so you should only do this if all connectors are safely wrapped in electrical tape.

[[Category:PineNote]]

File:Pn uart connection.jpg

2024-12-31T08:45:54Z

Mweigand: A picture of an UART connection between laptop and PineNote

== Summary ==
A picture of an UART connection between laptop and PineNote
== Licensing ==
{{PD|PD}}

PineNote

2024-12-30T07:29:47Z

Mweigand: /* State of the software */ add warning to remove lightdm in batch-2 PineNotes

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning|'''For Batch-2 (2024) PineNotes''': The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

{{Warning|'''For Batch-2 (2024) PineNotes''': The Batch 2 operating system is based on Debian Trixie, which is still in development flux. An issue with /lib64 symlinks was encountered for the specific built of the image that ships with the PineNotes of 2024. If you encounter update failures, please take a look at: [https://github.com/PNDeb/pinenote-debian-image/issues/99 this Github issues]}}

{{Warning|'''For Batch-2 (2024) PineNotes''': In order to prevent Gnome from starting after updates, it is recommend to uninstall the lightdm package: <code>sudo apt remove lightdm</code>}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* If you are looking for a working kernel for the PineNote, please see her: [https://github.com/m-weigand/linux/]
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

{{Note|As of November 2024 there is no working Android build available for the PineNote!}}

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch, the second batch (2024) ships with a purely passive pen)
* Optional Cover (included in the first and second production batches)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2024-12-30T07:25:08Z

Mweigand: /* State of the software */ Fix warnings

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning|**For Batch-2 (2024) PineNotes**: The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

{{Warning|**For Batch-2 (2024) PineNotes**: The Batch 2 operating system is based on Debian Trixie, which is still in development flux. An issue with /lib64 symlinks was encountered for the specific built of the image that ships with the PineNotes of 2024. If you encounter update failures, please take a look at: [https://github.com/PNDeb/pinenote-debian-image/issues/99 this Github issues]}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* If you are looking for a working kernel for the PineNote, please see her: [https://github.com/m-weigand/linux/]
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

{{Note|As of November 2024 there is no working Android build available for the PineNote!}}

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch, the second batch (2024) ships with a purely passive pen)
* Optional Cover (included in the first and second production batches)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2024-12-30T07:24:22Z

Mweigand: /* State of the software */ Add note regarding the /lib64 issue

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning:|**For Batch-2 (2024) PineNotes**: The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

{{Warning:**For Batch-2 (2024) PineNotes**: The Batch 2 operating system is based on Debian Trixie, which is still in development flux. An issue with /lib64 symlinks was encountered for the specific built of the image that ships with the PineNotes of 2024. If you encounter update failures, please take a look at: [https://github.com/PNDeb/pinenote-debian-image/issues/99 this Github issues]}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* If you are looking for a working kernel for the PineNote, please see her: [https://github.com/m-weigand/linux/]
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

{{Note|As of November 2024 there is no working Android build available for the PineNote!}}

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch, the second batch (2024) ships with a purely passive pen)
* Optional Cover (included in the first and second production batches)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2024-11-26T10:52:55Z

Mweigand: PineNote: Add link to working kernel

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* If you are looking for a working kernel for the PineNote, please see her: [https://github.com/m-weigand/linux/]
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

{{Note|As of November 2024 there is no working Android build available for the PineNote!}}

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch, the second batch (2024) ships with a purely passive pen)
* Optional Cover (included in the first and second production batches)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Software Releases

2024-11-26T10:51:41Z

Mweigand: PineNote: rearrange software release and add link to factory files for batch 2

This page contains a list of all available operating systems for the [[PineNote]] in alphabetical order.

== Debian ==

* A full GNOME-enabled disc image is provided under [https://github.com/m-weigand/pinenote-debian-recipes/releases m-weigand/pinenote-debian-recipes/releases]. This image can be flashed using rkdeveloptool.
{{Info|Check the [https://github.com/m-weigand/pinenote-debian-recipes/tree/trixie trixie] branch and github actions artifacts (possibly requires github login) for builds newer than the latest release.}}
Note that the second batch of PineNotes (from 2024) ships with this image based on Debian trixie. Images of the factory files (without the waveform data) can be found in this [https://github.com/PNDeb/pinenote-debian-image/releases/tag/batch-2-factory-image-wo-waveform Github release].
* A Debian-based minimalistic rootfs/disc image can be built using <code>debos</code> using the work from [https://salsa.debian.org/eugenrh Eugen Răhăian]. The GNOME image linked above is building on this work.

== Alpine ==

See https://github.com/DorianRudolph/pinenotes#alpine

== Arch Linux ==

See https://github.com/DorianRudolph/pinenotes#arch-linux
== postmarketOS ==

See https://wiki.postmarketos.org/wiki/PINE64_PineNote_(pine64-pinenote)

[[Category:PineNote]]

PineNote

2024-11-26T10:44:22Z

Mweigand: /* Accessories */

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

{{Note|As of November 2024 there is no working Android build available for the PineNote!}}

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch, the second batch (2024) ships with a purely passive pen)
* Optional Cover (included in the first and second production batches)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2024-11-26T10:43:40Z

Mweigand: /* Android: Add note that we do not have a working android at the moment*/

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

{{Note|As of November 2024 there is no working Android build available for the PineNote!}}

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Development/Booting Linux

2024-11-26T10:42:00Z

Mweigand: Add note that this page only refers to batch 1

{{Note|This page is only relevant for the first batch of PineNotes, sold in 2021/2022! Batch 2 (2024) PineNote come with linux pre-flashed!}}

To boot Linux, the stock U-Boot has to be patched.

Here the method from [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f charasyn] is used, based of work from Dorian as credited in the script. We'll use the script to pull the U-Boot environment out of the stock U-Boot partition. We'll then apply the patch, recreate the image, add a configuration file, and flash the new image to the PineNote.

== Steps to patch U-Boot ==

1. Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the Python tool]:

$ mkdir pinenote-uboot && cd pinenote-uboot
$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/boot-menu.patch -o boot-menu.patch
$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/pinenote-uboot-envtool.py -o pinenote-uboot-envtool.py
$ chmod o+x pinenote-uboot-envtool.py

2. Write your U-Boot partition to an image file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>

3. Extract the environment: <code>./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>

4. Poke around the files (or skip this if you don't like to learn...):

# Open <code>uboot.env</code> -- see, it's just text at this point!

# Open <code>boot-menu.patch</code> to get a feel for how that works

5. The boot-menu.patch makes assumptions about where your Linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.

6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>

{{Info|Note: Might fail with the following error: "''patch: **** unexpected end of file in patch at line 27''". In that case applying the patch manually is the solution.}}

7. Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>

8. Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>

9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to Android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.

10. Reboot into Linux

== Sources and further reading ==
# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.]

[[Category:PineNote]]

PineNote

2024-11-26T10:40:18Z

Mweigand: UART adapter: remove link to debian image and add note regarding asymmetric wiring

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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 single-board computer and powered by Rockchip RK3566 quad-core ARM Cortex-A55 64-bit SoC with Mali G52 GPU.

== Introduction ==

=== State of the software ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains a U-Boot build that prevents suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. This was caused by the unfortunate timing, so the factory ended up installing version of the operating system image that contained these issues. The required fixes are already available in the shipped Linux distribution, but they need to be [https://gist.github.com/m-weigand/efb1bef6097611d327533ab67b76903b installed manually] by the users.}}

The PineNote is based on the Rockchip RK3566 SoC, which was released in 2021. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer that uses the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific to the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024, the second PineNote batch was announced. This batch started shipping during the first half of November 2024 with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with Linux and embedded experience, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}
{{Warning|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}
{{Note|The UART adapter is not symmetrically wired, make sure to orient it with the components oriented towards the screen!}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle delivered with the PineNote allows you to have access to its serial console via USB-C Debug Accessory Mode (DAM) without having to disassemble the device. The factory-installed operating system runs the serial console at the 1,500,000 bps speed, 8 data bits and 1 stop bit, no parity, and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM: 4 GB LPDDR4
* Flash: 128 GB eMMC (soldered)

== Information, Schematics, and Certifications ==

Version v1.2 of the PineNote is the production version sold through the Pine Store as Developer Edition and Community Edition:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] When building a USB-C console breakout board, please be aware that a 10k CC pin pull-up is too weak to pull CC to a logically high level. Replacing it to a lower resistance, such as 1k, is recommended.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]] Developer Edition uses an active pen, which is different than the passive EMR pen described in the guide.

Version v1.1 of the PineNote is used by developers who received the early prototype, whose schematic is provided for reference only:
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2024-10-17T11:20:17Z

Mweigand: fix link to philosophy page

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024 the second batch of PineNotes was announced. This batch will ship with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with linux and embedded experience and, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://pine64.org/community/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}

The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accessory Mode (''DAM'') without having to open up the device.
The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

You can flash premade images with the following links:
* https://github.com/m-weigand/pinenote_uboot_patching_dorians_backup (Note: this creates a U-Boot image to flash, do not worry about idblock.bin on the instructions for the next link)
* https://github.com/m-weigand/pinenote-debian-recipes/releases/

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
Version v1.2 is the PineNote production version that was sold through the Pines64 store
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] Note: When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2024-10-17T10:23:22Z

Mweigand: Add a note regarding batch 2 and the Debian image

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

In October 2024 the second batch of PineNotes was announced. This batch will ship with a Debian-based operating system, currently developed here: [https://github.com/PNDeb/pinenote-debian-image]. Please note, however, that this batch is still aimed at developers with linux and embedded experience and, and should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.
* [[PineNote/Battery Replacement]]

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
{{Note|See main article: [[PineNote Development/UART]]}}

The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accessory Mode (''DAM'') without having to open up the device.
The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

It is relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

You can flash premade images with the following links:
* https://github.com/m-weigand/pinenote_uboot_patching_dorians_backup (Note: this creates a U-Boot image to flash, do not worry about idblock.bin on the instructions for the next link)
* https://github.com/m-weigand/pinenote-debian-recipes/releases/

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector, conforms to the USB Type-C Cable and Connector Specification

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
Version v1.2 is the PineNote production version that was sold through the Pines64 store
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
* [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
* [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] Note: When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
* [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
* [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]

Certifications:
* [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3566 SoC information:
* [https://files.pine64.org/doc/quartz64/Rockchip%20RK3566%20Datasheet%20V1.0-20201210.pdf Rockchip RK3566 ver 1.0 datasheet, release permission from Rockchip]

Rockchip RK817 PMU (Power Management Unit) Information:
* [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 version 1.01 datasheet]

LPDDR4 (200 Balls) SDRAM:
* ---

eMMC information:
* [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]

E-ink Panel information:
* [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
* [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]

Touch Screen information:
* [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
* Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]

G Sensor information:
* [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]

Audio Amplifier information:
* [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Resources ==
* [[PineNote Press]]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Development/Flashing

2023-02-04T12:54:22Z

Mweigand: add links back to PN main page

{{Under construction}}

{{Info|These instructions are directed towards experienced developers only!}}

This page contains information on flashing software to the [https://wiki.pine64.org/wiki/PineNote PineNote].

Currently, software can be flashed using rkdeveloptool or from the factory Android installation (UART shell, adb, or fastboot).

== Backup ==

{{Info|A backup of the content of the internal eMMC before anything gets messed is '''mandatory'''.}}

Especially the ''waveform'' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like U-Boot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large ''userdata'' partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched U-Boo for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

Build rkdeveloptool:

git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..

Download mode
Enter the download mode by placing the pen as pictured below. A magnet placed where the pen's cap is should also work (haven't tried). I guess the dot on the case also indicates the position of the sensor.

placing pen on the back

<code>lsusb</code> should now recognize the PineNote as:

2207:350a Fuzhou Rockchip Electronics Company USB download gadget

List partitions:

> rkdeveloptool list-partitions
# LBA start (sectors) LBA end (sectors) Size (bytes) Name
00 16384 24575 4194304 uboot
01 24576 32767 4194304 trust
02 32768 36863 2097152 waveform
03 36864 45055 4194304 misc
04 45056 53247 4194304 dtbo
05 53248 55295 1048576 vbmeta
06 55296 137215 41943040 boot
07 137216 145407 4194304 security
08 145408 407551 134217728 recovery
09 407552 1193983 402653184 backup
10 1193984 3291135 1073741824 cache
11 3291136 3323903 16777216 metadata
12 3323904 9697279 3263168512 super
13 9697280 9730047 16777216 logo
14 9730048 9861119 67108864 device
15 9861120 241827775 118766927872 userdata

{{Warning|this process is very new! Proceed at your own risk.}}

See [https://github.com/m-weigand/pinenote-debian-recipes/releases/tag/v0.1 instructions on this artifact]. It will instruct you on extracting the rootfs into an empty ext4 partition. This can be done from Linux or Android. Further instructions on building your own rootfs [https://github.com/m-weigand/pinenote-debian-recipes can be found here].

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk.

It also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
TODO

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using ''dd''.

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the eMMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the current version (current as of 2022-01-02), there might have to be made a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that ''Loader'' here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays ''Maskrom'' (not ''Loader'') from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ''ctrl-c'' (while attached using an UART dongle)
# While in u-boot use the command <code>rockusb 0 mmc 0</code> to start Rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between U-Boot and Rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

./rkdeveloptool list

It should output something like "''DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom''". If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:

./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin

This should output "''Downloading bootloader succeeded''".

We can now verify that this worked using e.g. the "read flash info" command:

./rkdeveloptool read-flash-info

{{Note|'''TODO:''' Section needs to be finished}}

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for [[PineNote Development/Flashing#Creating a mainline boot image|Creating a mainline boot image]], but instead of flashing it with ''rkdeveloptool'', use ''fastboot''. You can enter fastboot in either of two ways:

* Use "reboot bootloader" from adb or a UART console or
* get a U-Boot prompt and run <code>fastboot usb 0</code>.

[[Category:PineNote]]

PineNote Development/Building Kernel

2023-02-04T12:48:54Z

Mweigand: start restructuring the building_kernel page for the PineNote

This page contains information on how to build a linux kernel for the [https://wiki.pine64.org/wiki/PineNote PineNote].

= Available Kernel Repositories =

The following (incomplete?) PineNote-specific kernel repositories are available:

* https://github.com/m-weigand/linux/ (based mainly on the repository from smaeul, with additional patches pulled in from other sources, Debian packages available)
* https://gitlab.com/pgwipeout/linux-next/
* https://github.com/smaeul/linux/tree/rk35/pinenote-next
* https://pine64.cknow.org/kernel/ A rebasing effort to kernel 6.2 (Debian packages available for testing)

= Building the kernel =

{{Info|These following instructions need to be cleaned up and updated, and OS-specific information and tweaks should be moved elsewhere}}

After following [https://github.com/DorianRudolph/pinenotes#starter-guide Dorian's directions] to get Arch installed you've seen someone [https://github.com/m-weigand/mw_pinenote_misc/blob/main/videos/20220808_bw_dither_mode_picture_doom_video_small.mp4 playing DOOM] and you want to learn how to get the features that enable that kind of performance. To get your PN running this smoothly, we'll need to build our own kernel. There are two kernel efforts underway right now:

# pgwipeout: https://gitlab.com/pgwipeout/linux-next
# smaeul: https://github.com/smaeul/linux/tree/rk35/pinenote-next

We'll be using smaeul's kernel + some additional patches provided by DorianRudolph, pgwipeout, Maximilian Weigand, occam_razor, and hrdl. Thanks so much to them, and all the other users who have worked on piecing together drivers, twiddling configs, answering questions, and sharing their work in other ways. Brava!

Perhaps the main component of the kernel is the DRM driver. You can read more about the driver by reading [https://lore.kernel.org/linux-rockchip/20220413221916.50995-1-samuel@sholland.org/T/ Smaeul's RFC].

=== A small warning ===

This guide is completely based off of the scripts provided by Maximilian. We'll be cloning and running them, but he owns them and he -- or others -- might change them. It's smart to have a look at what's going on, check when this page was last updated vs when his scripts were last updated, etc. Be nimble!

Additionally, as Maximilian warns [https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches here], these changes are all experimental and may damage your panel.

{{info|If anyone reading this has recommended reading for how we can understand what may damage our panels (IE is the risk in fast updates? The types of updates? something more complicated?), please add it here!}}

== What you should have already done ==

It is assumed you've already got an operating system installed on your Pinenote other than the stock Android. Doing this isn't trivial, but it is well understood - you will be following the footsteps of many others. Dorian Rudolph made a guide for doing this, available [https://github.com/DorianRudolph/pinenotes#starter-guide here].

== What do you need to know? ==

If you followed Dorian's guide to get here and felt semi-comfortable, you'll be fine. This is no more complicated than that. If you are intimidated, that's okay! I'll still encourage you to try :) you will learn a lot, just be patient and don't put any data on your PineNote that you wouldn't be okay losing. If you run into trouble, ask for help in the [https://discord.com/invite/pine64 Discord]/[https://matrix.to/#/#pinenote:matrix.org Matrix]. Please try to solve problems on your own first, and then ask for help -- if nobody replies, please be patient and ask again soon.

== Steps to build ==

1. Clone Maximilian's scripts:

$ git clone https://github.com/m-weigand/mw_pinenote_misc.git

2. Make a separate directory for patching the kernel. Then run Maximilian's ''clone_and_prepare_git.sh''. This will clone smaeul's kernel and a number of patches. Read the script to see which patches it is using. Feel free to open the patches too -- it's helpful to get a slim idea of what's going on, if only looking at the commit messages in them:

$ cd ../
$ sh mw_pinenote_misc/custom_kernel/clone_and_prepare_git.sh

3. Compile the kernel:

$ sh ./mw_pinenote_misc/custom_kernel/compile.sh

4. Next we want to perform the work captured in '''install_to_pn.sh''', but the work may vary slightly from person to person. As long as you put them somewhere and configure your '''extlinux.conf''' to point at it, things will be okay. Looking at '''install_to_pn.sh''', we can see that there are three pieces to installing the kernel: the kernel image (called ''Image''), the device tree (''rk3566-pinenote-v1.2.dtb''), and the modules. All of these files have been compiled and placed into the '''linux/pack''' folder. The easiest way to send these over is by using ''scp'' or ''rsync'' - read the script and decide how you would like to get your files in the correct location. You may need to install ''rsync'' on your PineNote if it doesn't already have it.

5. DTB was installed like this: <code>$ scp rk3566-pinenote-v1.2.dtb root@pinenote:/boot/dtbs/rockchip/</code>

6. After installing the DTB as above, the file '''/boot/extlinux/extlinux.conf''' may be updated to point to this new file

7. (Perhaps not necessary?) The last step is to generate a new initrd image (see [https://en.wikipedia.org/wiki/Initial_ramdisk Wikipedia] for an explanation about initial ramdisk). This is done on the PineNote itself. Send Maximilian's installation script over and run it. Then place the generated image (from the last step of the shell script) into your boot partition and update '''extlinux.conf''' if needed to point at this new file.

$ scp initrd/gen_uboot_image.sh root@pinenote:/root # Do this part on local to put script on PN
$ ssh root@pinenote # Or use UART, the dongle + picocom, and change to root
$ cd /root
$ ./gen_uboot_image.sh
$ mv initrd.img /boot/initrd.img
$ vim /boot/extlinux/extlinux.conf # Update this to reference this new initrd image

8. At this point your kernel is in place! However, there are a few more steps you may need to complete to ensure the display and networking continue to work:
* For display, you may need to change '''/lib/firmware/waveform.bin''' to '''/lib/firmware/rockchip/ebc.wbf''' (TODO: is this a difference between PG and smaeul's kernel or a patch?)
* For networking, you may need to change '''/lib/firmware/pinenote.bin''' to '''/lib/firmware/pinenote-v1.2.bin'''

9. This part technically isn't kernel specific, but we need to install a patched version of Mesa. If you are running an Arch based system, you're in luck! occam_razor provides prebuilt patched packages (say that 5 times fast) [https://github.com/0cc4m/pinenote-misc/releases here]. Simply extract these files, send them to PN, and install them using the package manager. You can also patch it yourself by looking at Maximilian's [https://github.com/m-weigand/mw_pinenote_misc/blob/main/compile_mesa.sh compile_mesa.sh].

{{Info|If you frequently update your system with ''pacman -Syu'', you will end up updating these packages and losing the patches. Add this line to your <code>/etc/pacman.conf</code> to prevent them from being updated: <pre>IgnorePkg = libva-mesa-driver mesa mesa-debug mesa-vdpau opencl-mesa vulkan-mesa-layers vulkan-broadcom vulkan-panfrost vulkan-radeon vulkan-swrast</pre>}}

10. To ensure the GPU stays on, we need to use Maximilian's [https://github.com/m-weigand/mw_pinenote_misc/blob/main/systemd/mweigand_eglinfo.service mweigand_eglinfo.service]. The ''Readme.md'' in that same directory has instructions for how to install this, but basically we need to copy it to '''/etc/systemd/system/''', run <code>sudo systemctl daemon-reload</code> to make sure systemd knows it exists, then execute <code>sudo systemctl enable mweigand_eglinfo.service</code>.

= Next steps =
== Configuring the driver ==
The driver has several options that can improve performance. These can be read about [https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#new-features-as-of-2022august08 here]. <code>rockchip_ebc.bw_mode=1 rockchip_ebc.default_waveform=1 rockchip_ebc.refresh_threshold=30 rockchip_ebc.auto_refresh=1</code> may be used to make the image lower quality, but much faster to update. The auto_refresh setting is also essential to clear ghosting which will otherwise accrue on screen. The ''APPEND'' line in the '''extlinux.conf''' might be added to make sure they are applied on boot.

== Fixing suspend ==
If you're using a logind system, edit your '''/etc/systemd/logind.conf''' config. More information on what to do [https://wiki.archlinux.org/title/Power_management#ACPI_event in Arch's documentation].

== Configuring your apps ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps this page].

== Booting Linux instead of Android ==
[[PineNote Development/Booting Linux]]

== Fixing Bluetooth ==
See [[PineNote Development/Software Tweaks]]

[[Category:PineNote]]

PineNote Development/Building Kernel

2023-02-04T12:31:44Z

Mweigand: Add link to the PN main page

This page contains information on how to build a linux kernel for the [https://wiki.pine64.org/wiki/PineNote PineNote].

= Building the kernel =

After following [https://github.com/DorianRudolph/pinenotes#starter-guide Dorian's directions] to get Arch installed you've seen someone [https://github.com/m-weigand/mw_pinenote_misc/blob/main/videos/20220808_bw_dither_mode_picture_doom_video_small.mp4 playing DOOM] and you want to learn how to get the features that enable that kind of performance. To get your PN running this smoothly, we'll need to build our own kernel. There are two kernel efforts underway right now:

# pgwipeout: https://gitlab.com/pgwipeout/linux-next
# smaeul: https://github.com/smaeul/linux/tree/rk35/pinenote-next

We'll be using smaeul's kernel + some additional patches provided by DorianRudolph, pgwipeout, Maximilian Weigand, occam_razor, and hrdl. Thanks so much to them, and all the other users who have worked on piecing together drivers, twiddling configs, answering questions, and sharing their work in other ways. Brava!

Perhaps the main component of the kernel is the DRM driver. You can read more about the driver by reading [https://lore.kernel.org/linux-rockchip/20220413221916.50995-1-samuel@sholland.org/T/ Smaeul's RFC].

=== A small warning ===

This guide is completely based off of the scripts provided by Maximilian. We'll be cloning and running them, but he owns them and he -- or others -- might change them. It's smart to have a look at what's going on, check when this page was last updated vs when his scripts were last updated, etc. Be nimble!

Additionally, as Maximilian warns [https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches here], these changes are all experimental and may damage your panel.

{{info|If anyone reading this has recommended reading for how we can understand what may damage our panels (IE is the risk in fast updates? The types of updates? something more complicated?), please add it here!}}

== What you should have already done ==

It is assumed you've already got an operating system installed on your Pinenote other than the stock Android. Doing this isn't trivial, but it is well understood - you will be following the footsteps of many others. Dorian Rudolph made a guide for doing this, available [https://github.com/DorianRudolph/pinenotes#starter-guide here].

== What do you need to know? ==

If you followed Dorian's guide to get here and felt semi-comfortable, you'll be fine. This is no more complicated than that. If you are intimidated, that's okay! I'll still encourage you to try :) you will learn a lot, just be patient and don't put any data on your PineNote that you wouldn't be okay losing. If you run into trouble, ask for help in the [https://discord.com/invite/pine64 Discord]/[https://matrix.to/#/#pinenote:matrix.org Matrix]. Please try to solve problems on your own first, and then ask for help -- if nobody replies, please be patient and ask again soon.

== Steps to build ==

1. Clone Maximilian's scripts:

$ git clone https://github.com/m-weigand/mw_pinenote_misc.git

2. Make a separate directory for patching the kernel. Then run Maximilian's ''clone_and_prepare_git.sh''. This will clone smaeul's kernel and a number of patches. Read the script to see which patches it is using. Feel free to open the patches too -- it's helpful to get a slim idea of what's going on, if only looking at the commit messages in them:

$ cd ../
$ sh mw_pinenote_misc/custom_kernel/clone_and_prepare_git.sh

3. Compile the kernel:

$ sh ./mw_pinenote_misc/custom_kernel/compile.sh

4. Next we want to perform the work captured in '''install_to_pn.sh''', but the work may vary slightly from person to person. As long as you put them somewhere and configure your '''extlinux.conf''' to point at it, things will be okay. Looking at '''install_to_pn.sh''', we can see that there are three pieces to installing the kernel: the kernel image (called ''Image''), the device tree (''rk3566-pinenote-v1.2.dtb''), and the modules. All of these files have been compiled and placed into the '''linux/pack''' folder. The easiest way to send these over is by using ''scp'' or ''rsync'' - read the script and decide how you would like to get your files in the correct location. You may need to install ''rsync'' on your PineNote if it doesn't already have it.

5. DTB was installed like this: <code>$ scp rk3566-pinenote-v1.2.dtb root@pinenote:/boot/dtbs/rockchip/</code>

6. After installing the DTB as above, the file '''/boot/extlinux/extlinux.conf''' may be updated to point to this new file

7. (Perhaps not necessary?) The last step is to generate a new initrd image (see [https://en.wikipedia.org/wiki/Initial_ramdisk Wikipedia] for an explanation about initial ramdisk). This is done on the PineNote itself. Send Maximilian's installation script over and run it. Then place the generated image (from the last step of the shell script) into your boot partition and update '''extlinux.conf''' if needed to point at this new file.

$ scp initrd/gen_uboot_image.sh root@pinenote:/root # Do this part on local to put script on PN
$ ssh root@pinenote # Or use UART, the dongle + picocom, and change to root
$ cd /root
$ ./gen_uboot_image.sh
$ mv initrd.img /boot/initrd.img
$ vim /boot/extlinux/extlinux.conf # Update this to reference this new initrd image

8. At this point your kernel is in place! However, there are a few more steps you may need to complete to ensure the display and networking continue to work:
* For display, you may need to change '''/lib/firmware/waveform.bin''' to '''/lib/firmware/rockchip/ebc.wbf''' (TODO: is this a difference between PG and smaeul's kernel or a patch?)
* For networking, you may need to change '''/lib/firmware/pinenote.bin''' to '''/lib/firmware/pinenote-v1.2.bin'''

9. This part technically isn't kernel specific, but we need to install a patched version of Mesa. If you are running an Arch based system, you're in luck! occam_razor provides prebuilt patched packages (say that 5 times fast) [https://github.com/0cc4m/pinenote-misc/releases here]. Simply extract these files, send them to PN, and install them using the package manager. You can also patch it yourself by looking at Maximilian's [https://github.com/m-weigand/mw_pinenote_misc/blob/main/compile_mesa.sh compile_mesa.sh].

{{Info|If you frequently update your system with ''pacman -Syu'', you will end up updating these packages and losing the patches. Add this line to your <code>/etc/pacman.conf</code> to prevent them from being updated: <pre>IgnorePkg = libva-mesa-driver mesa mesa-debug mesa-vdpau opencl-mesa vulkan-mesa-layers vulkan-broadcom vulkan-panfrost vulkan-radeon vulkan-swrast</pre>}}

10. To ensure the GPU stays on, we need to use Maximilian's [https://github.com/m-weigand/mw_pinenote_misc/blob/main/systemd/mweigand_eglinfo.service mweigand_eglinfo.service]. The ''Readme.md'' in that same directory has instructions for how to install this, but basically we need to copy it to '''/etc/systemd/system/''', run <code>sudo systemctl daemon-reload</code> to make sure systemd knows it exists, then execute <code>sudo systemctl enable mweigand_eglinfo.service</code>.

= Next steps =
== Configuring the driver ==
The driver has several options that can improve performance. These can be read about [https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#new-features-as-of-2022august08 here]. <code>rockchip_ebc.bw_mode=1 rockchip_ebc.default_waveform=1 rockchip_ebc.refresh_threshold=30 rockchip_ebc.auto_refresh=1</code> may be used to make the image lower quality, but much faster to update. The auto_refresh setting is also essential to clear ghosting which will otherwise accrue on screen. The ''APPEND'' line in the '''extlinux.conf''' might be added to make sure they are applied on boot.

== Fixing suspend ==
If you're using a logind system, edit your '''/etc/systemd/logind.conf''' config. More information on what to do [https://wiki.archlinux.org/title/Power_management#ACPI_event in Arch's documentation].

== Configuring your apps ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps this page].

== Booting Linux instead of Android ==
[[PineNote Development/Booting Linux]]

== Fixing Bluetooth ==
See [[PineNote Development/Software Tweaks]]

[[Category:PineNote]]

PineNote Development/Apps

2023-02-04T12:29:22Z

Mweigand:

This page lists applications and tweaks for the [https://wiki.pine64.org/wiki/PineNote PineNote].

= Development =

Here are some resources you may find helpful in learning to develop on embedded Linux devices:
* Great YouTube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

Emulator recommendation for developing and testing PineNote apps: https://github.com/michaelshiel/picom-epaper

The PineNote is a specialized device, mainly due to the eink display having unique display and refresh characteristics.
Finding and configuring apps that work well sometimes requires a lot of tweaking and a lot exploring, especially for
applications containing fast screen updates and animations, as well as depend on a lot of colors.

[https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] showing the performance of a few applications.

= Desktop Environments =

=== Sway ===

* [https://github.com/hmpthcs/WinkShell WinkShell] "Collected applications, configurations and scripts for using a wlroots-based compositor with an EPD (aka e-ink display). Currently supports Sway only."

* [https://github.com/0cc4m/pinenote-misc/blob/main/sway/config/sway/config 0cc4m's config]

==== Getting touch + pen working on sway ====

If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set <code>rockchip_ebc.panel_reflection=0</code> on boot (see [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Configuring_the_driver this page] for more info). Add the following line to your sway config:
<pre>
# This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html
input "type:table_tool" calibration_matrix -1 0 1 0 -1 1
</pre>

=== Gnome ===

Gnome on wayland runs nicely on the PineNote. However, a slightly patched version of mutter is required at the moment.

* See this repository for .deb packages and patch/compile files: [https://github.com/m-weigand/pinenote_debian_mutter Patched Debian Mutter for Bookworm]
* The ready-to-use [https://github.com/m-weigand/pinenote-debian-recipes/releases Debian image] provides a pre-configured GNOME environment], with specific GNOME configurations found [https://github.com/m-weigand/pinenote-debian-recipes/blob/main/overlays/gnome_config/01-pinenote-settings here]
* A GNOME extension is being [https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension developed] that provides access to some of the ebc-specific driver options.
* [https://github.com/MichiMolle/PNEink PNEink] is a GNOME Theme for use with the PineNote

==== GTK3 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk3-eink here].

==== GTK4 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk4-eink here].

= Application support on the PineNote =

== System-Control ==

* A rust-based dbus service is being [https://github.com/m-weigand/pinenote_dbus_service developed] to enable easy, system-wide control over some of the PineNote-specific settings by users and programs (e.g., triggering global screen refreshes, changing waveforms, enabling/disabling dithering). Requires [https://github.com/m-weigand/linux/releases this kernel].

== Notetaking ==

=== Xournal++ ===
Works well, writing is pretty quick. The development version supports PDF highlighting, links, and offers repainting-related optimisations (https://github.com/xournalpp/xournalpp/commit/c0a91f02afbfb67a60f7088b4c579a796693e05d and https://github.com/xournalpp/xournalpp/commit/ce1c66cb6d78f3332714ca21d279cf20548d7c06). To improve the performance even further apply https://github.com/xournalpp/xournalpp/pull/4158 and https://github.com/xournalpp/xournalpp/pull/4611 while on master.

Xournal++ uses anti-aliasing and interpolation, which do not work well for the A1 waveform. Mitigations include using either dithering or black-white mode in the ebc driver, or compiling Xournal++ with https://gitlab.com/hrdl/pinenote-shared/-/blob/main/patches/xournalpp/0001-Disable-anti-aliasing-and-use-NEAREST-interpolation-.patch.

Pre-compiled Debian packages with some of the PineNote-related modifications and support for triggering global refreshes after scrolling using the dbus service (see above) can be found [https://github.com/m-weigand/xournalpp_pn/releases here]

=== Obsidian ===
Works well, EInk-Theme can be found [https://github.com/MichiMolle/obsidian-eink here].

== Web Browsing ==

=== Firefox ===
Pretty good experience! Enabling GPU acceleration is helpful.

==== GPU Acceleration in Firefox ====
See [https://github.com/0cc4m/pinenote-misc#firefox-hardware-acceleration 0ccam's notes here].

== "Cloud" ==
=== syncthing ===
High contrast theme can be found [https://github.com/MichiMolle/syncthing-eink here].

[[Category:PineNote]]

PineNote Development/Apps

2023-02-04T12:26:43Z

Mweigand: /* Xournal++ */

= Development =

Here are some resources you may find helpful in learning to develop on embedded Linux devices:
* Great YouTube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

Emulator recommendation for developing and testing PineNote apps: https://github.com/michaelshiel/picom-epaper

The PineNote is a specialized device, mainly due to the eink display having unique display and refresh characteristics.
Finding and configuring apps that work well sometimes requires a lot of tweaking and a lot exploring, especially for
applications containing fast screen updates and animations, as well as depend on a lot of colors.

[https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] showing the performance of a few applications.

= Desktop Environments =

=== Sway ===

* [https://github.com/hmpthcs/WinkShell WinkShell] "Collected applications, configurations and scripts for using a wlroots-based compositor with an EPD (aka e-ink display). Currently supports Sway only."

* [https://github.com/0cc4m/pinenote-misc/blob/main/sway/config/sway/config 0cc4m's config]

==== Getting touch + pen working on sway ====

If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set <code>rockchip_ebc.panel_reflection=0</code> on boot (see [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Configuring_the_driver this page] for more info). Add the following line to your sway config:
<pre>
# This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html
input "type:table_tool" calibration_matrix -1 0 1 0 -1 1
</pre>

=== Gnome ===

Gnome on wayland runs nicely on the PineNote. However, a slightly patched version of mutter is required at the moment.

* See this repository for .deb packages and patch/compile files: [https://github.com/m-weigand/pinenote_debian_mutter Patched Debian Mutter for Bookworm]
* The ready-to-use [https://github.com/m-weigand/pinenote-debian-recipes/releases Debian image] provides a pre-configured GNOME environment], with specific GNOME configurations found [https://github.com/m-weigand/pinenote-debian-recipes/blob/main/overlays/gnome_config/01-pinenote-settings here]
* A GNOME extension is being [https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension developed] that provides access to some of the ebc-specific driver options.
* [https://github.com/MichiMolle/PNEink PNEink] is a GNOME Theme for use with the PineNote

==== GTK3 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk3-eink here].

==== GTK4 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk4-eink here].

= Application support on the PineNote =

== System-Control ==

* A rust-based dbus service is being [https://github.com/m-weigand/pinenote_dbus_service developed] to enable easy, system-wide control over some of the PineNote-specific settings by users and programs (e.g., triggering global screen refreshes, changing waveforms, enabling/disabling dithering). Requires [https://github.com/m-weigand/linux/releases this kernel].

== Notetaking ==

=== Xournal++ ===
Works well, writing is pretty quick. The development version supports PDF highlighting, links, and offers repainting-related optimisations (https://github.com/xournalpp/xournalpp/commit/c0a91f02afbfb67a60f7088b4c579a796693e05d and https://github.com/xournalpp/xournalpp/commit/ce1c66cb6d78f3332714ca21d279cf20548d7c06). To improve the performance even further apply https://github.com/xournalpp/xournalpp/pull/4158 and https://github.com/xournalpp/xournalpp/pull/4611 while on master.

Xournal++ uses anti-aliasing and interpolation, which do not work well for the A1 waveform. Mitigations include using either dithering or black-white mode in the ebc driver, or compiling Xournal++ with https://gitlab.com/hrdl/pinenote-shared/-/blob/main/patches/xournalpp/0001-Disable-anti-aliasing-and-use-NEAREST-interpolation-.patch.

Pre-compiled Debian packages with some of the PineNote-related modifications and support for triggering global refreshes after scrolling using the dbus service (see above) can be found [https://github.com/m-weigand/xournalpp_pn/releases here]

=== Obsidian ===
Works well, EInk-Theme can be found [https://github.com/MichiMolle/obsidian-eink here].

== Web Browsing ==

=== Firefox ===
Pretty good experience! Enabling GPU acceleration is helpful.

==== GPU Acceleration in Firefox ====
See [https://github.com/0cc4m/pinenote-misc#firefox-hardware-acceleration 0ccam's notes here].

== "Cloud" ==
=== syncthing ===
High contrast theme can be found [https://github.com/MichiMolle/syncthing-eink here].

[[Category:PineNote]]

PineNote Development/Apps

2023-02-04T12:22:17Z

Mweigand: Add dbus service program to the application list

= Development =

Here are some resources you may find helpful in learning to develop on embedded Linux devices:
* Great YouTube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

Emulator recommendation for developing and testing PineNote apps: https://github.com/michaelshiel/picom-epaper

The PineNote is a specialized device, mainly due to the eink display having unique display and refresh characteristics.
Finding and configuring apps that work well sometimes requires a lot of tweaking and a lot exploring, especially for
applications containing fast screen updates and animations, as well as depend on a lot of colors.

[https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] showing the performance of a few applications.

= Desktop Environments =

=== Sway ===

* [https://github.com/hmpthcs/WinkShell WinkShell] "Collected applications, configurations and scripts for using a wlroots-based compositor with an EPD (aka e-ink display). Currently supports Sway only."

* [https://github.com/0cc4m/pinenote-misc/blob/main/sway/config/sway/config 0cc4m's config]

==== Getting touch + pen working on sway ====

If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set <code>rockchip_ebc.panel_reflection=0</code> on boot (see [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Configuring_the_driver this page] for more info). Add the following line to your sway config:
<pre>
# This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html
input "type:table_tool" calibration_matrix -1 0 1 0 -1 1
</pre>

=== Gnome ===

Gnome on wayland runs nicely on the PineNote. However, a slightly patched version of mutter is required at the moment.

* See this repository for .deb packages and patch/compile files: [https://github.com/m-weigand/pinenote_debian_mutter Patched Debian Mutter for Bookworm]
* The ready-to-use [https://github.com/m-weigand/pinenote-debian-recipes/releases Debian image] provides a pre-configured GNOME environment], with specific GNOME configurations found [https://github.com/m-weigand/pinenote-debian-recipes/blob/main/overlays/gnome_config/01-pinenote-settings here]
* A GNOME extension is being [https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension developed] that provides access to some of the ebc-specific driver options.
* [https://github.com/MichiMolle/PNEink PNEink] is a GNOME Theme for use with the PineNote

==== GTK3 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk3-eink here].

==== GTK4 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk4-eink here].

= Application support on the PineNote =

== System-Control ==

* A rust-based dbus service is being [https://github.com/m-weigand/pinenote_dbus_service developed] to enable easy, system-wide control over some of the PineNote-specific settings by users and programs (e.g., triggering global screen refreshes, changing waveforms, enabling/disabling dithering). Requires [https://github.com/m-weigand/linux/releases this kernel].

== Notetaking ==

=== Xournal++ ===
Works well, writing is pretty quick. The development version supports PDF highlighting, links, and offers repainting-related optimisations (https://github.com/xournalpp/xournalpp/commit/c0a91f02afbfb67a60f7088b4c579a796693e05d and https://github.com/xournalpp/xournalpp/commit/ce1c66cb6d78f3332714ca21d279cf20548d7c06). To improve the performance even further apply https://github.com/xournalpp/xournalpp/pull/4158 and https://github.com/xournalpp/xournalpp/pull/4611 while on master.

Xournal++ uses anti-aliasing and interpolation, which do not work well for the A1 waveform. Mitigations include using either dithering or black-white mode in the ebc driver, or compiling Xournal++ with https://gitlab.com/hrdl/pinenote-shared/-/blob/main/patches/xournalpp/0001-Disable-anti-aliasing-and-use-NEAREST-interpolation-.patch.

=== Obsidian ===
Works well, EInk-Theme can be found [https://github.com/MichiMolle/obsidian-eink here].

== Web Browsing ==

=== Firefox ===
Pretty good experience! Enabling GPU acceleration is helpful.

==== GPU Acceleration in Firefox ====
See [https://github.com/0cc4m/pinenote-misc#firefox-hardware-acceleration 0ccam's notes here].

== "Cloud" ==
=== syncthing ===
High contrast theme can be found [https://github.com/MichiMolle/syncthing-eink here].

[[Category:PineNote]]

PineNote Development/Apps

2023-02-04T12:18:40Z

Mweigand: /* Gnome */

= Development =

Here are some resources you may find helpful in learning to develop on embedded Linux devices:
* Great YouTube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

Emulator recommendation for developing and testing PineNote apps: https://github.com/michaelshiel/picom-epaper

The PineNote is a specialized device, mainly due to the eink display having unique display and refresh characteristics.
Finding and configuring apps that work well sometimes requires a lot of tweaking and a lot exploring, especially for
applications containing fast screen updates and animations, as well as depend on a lot of colors.

[https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] showing the performance of a few applications.

= Desktop Environments =

=== Sway ===

* [https://github.com/hmpthcs/WinkShell WinkShell] "Collected applications, configurations and scripts for using a wlroots-based compositor with an EPD (aka e-ink display). Currently supports Sway only."

* [https://github.com/0cc4m/pinenote-misc/blob/main/sway/config/sway/config 0cc4m's config]

==== Getting touch + pen working on sway ====

If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set <code>rockchip_ebc.panel_reflection=0</code> on boot (see [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Configuring_the_driver this page] for more info). Add the following line to your sway config:
<pre>
# This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html
input "type:table_tool" calibration_matrix -1 0 1 0 -1 1
</pre>

=== Gnome ===

Gnome on wayland runs nicely on the PineNote. However, a slightly patched version of mutter is required at the moment.

* See this repository for .deb packages and patch/compile files: [https://github.com/m-weigand/pinenote_debian_mutter Patched Debian Mutter for Bookworm]
* The ready-to-use [https://github.com/m-weigand/pinenote-debian-recipes/releases Debian image] provides a pre-configured GNOME environment], with specific GNOME configurations found [https://github.com/m-weigand/pinenote-debian-recipes/blob/main/overlays/gnome_config/01-pinenote-settings here]
* A GNOME extension is being [https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension developed] that provides access to some of the ebc-specific driver options.
* [https://github.com/MichiMolle/PNEink PNEink] is a GNOME Theme for use with the PineNote

==== GTK3 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk3-eink here].

==== GTK4 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk4-eink here].

= Application support on the PineNote =
== Notetaking ==

=== Xournal++ ===
Works well, writing is pretty quick. The development version supports PDF highlighting, links, and offers repainting-related optimisations (https://github.com/xournalpp/xournalpp/commit/c0a91f02afbfb67a60f7088b4c579a796693e05d and https://github.com/xournalpp/xournalpp/commit/ce1c66cb6d78f3332714ca21d279cf20548d7c06). To improve the performance even further apply https://github.com/xournalpp/xournalpp/pull/4158 and https://github.com/xournalpp/xournalpp/pull/4611 while on master.

Xournal++ uses anti-aliasing and interpolation, which do not work well for the A1 waveform. Mitigations include using either dithering or black-white mode in the ebc driver, or compiling Xournal++ with https://gitlab.com/hrdl/pinenote-shared/-/blob/main/patches/xournalpp/0001-Disable-anti-aliasing-and-use-NEAREST-interpolation-.patch.

=== Obsidian ===
Works well, EInk-Theme can be found [https://github.com/MichiMolle/obsidian-eink here].

== Web Browsing ==

=== Firefox ===
Pretty good experience! Enabling GPU acceleration is helpful.

==== GPU Acceleration in Firefox ====
See [https://github.com/0cc4m/pinenote-misc#firefox-hardware-acceleration 0ccam's notes here].

== "Cloud" ==
=== syncthing ===
High contrast theme can be found [https://github.com/MichiMolle/syncthing-eink here].

[[Category:PineNote]]

PineNote Development/Apps

2023-02-04T12:17:14Z

Mweigand: Add information to the GNOME section

= Development =

Here are some resources you may find helpful in learning to develop on embedded Linux devices:
* Great YouTube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

Emulator recommendation for developing and testing PineNote apps: https://github.com/michaelshiel/picom-epaper

The PineNote is a specialized device, mainly due to the eink display having unique display and refresh characteristics.
Finding and configuring apps that work well sometimes requires a lot of tweaking and a lot exploring, especially for
applications containing fast screen updates and animations, as well as depend on a lot of colors.

[https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] showing the performance of a few applications.

= Desktop Environments =

=== Sway ===

* [https://github.com/hmpthcs/WinkShell WinkShell] "Collected applications, configurations and scripts for using a wlroots-based compositor with an EPD (aka e-ink display). Currently supports Sway only."

* [https://github.com/0cc4m/pinenote-misc/blob/main/sway/config/sway/config 0cc4m's config]

==== Getting touch + pen working on sway ====

If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set <code>rockchip_ebc.panel_reflection=0</code> on boot (see [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Configuring_the_driver this page] for more info). Add the following line to your sway config:
<pre>
# This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html
input "type:table_tool" calibration_matrix -1 0 1 0 -1 1
</pre>

=== Gnome ===

Gnome on wayland runs nicely on the PineNote. However, a slightly patched version of mutter is required at the moment.

* See this repository for .deb packages and patch/compile files: [https://github.com/m-weigand/pinenote_debian_mutter Patched Debian Mutter for Bookworm]
* The ready-to-use [https://github.com/m-weigand/pinenote-debian-recipes/releases Debian image] provides a pre-configured GNOME environment], with specific GNOME configurations found [https://github.com/m-weigand/pinenote-debian-recipes/blob/main/overlays/gnome_config/01-pinenote-settings here]
* A GNOME extension is being [https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension developed] that provides access to some of the ebc-specific driver options.

==== GTK3 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk3-eink here].

==== GTK4 ====
High contrast style for eink-devices can be found [https://github.com/MichiMolle/gtk4-eink here].

= Application support on the PineNote =
== Notetaking ==

=== Xournal++ ===
Works well, writing is pretty quick. The development version supports PDF highlighting, links, and offers repainting-related optimisations (https://github.com/xournalpp/xournalpp/commit/c0a91f02afbfb67a60f7088b4c579a796693e05d and https://github.com/xournalpp/xournalpp/commit/ce1c66cb6d78f3332714ca21d279cf20548d7c06). To improve the performance even further apply https://github.com/xournalpp/xournalpp/pull/4158 and https://github.com/xournalpp/xournalpp/pull/4611 while on master.

Xournal++ uses anti-aliasing and interpolation, which do not work well for the A1 waveform. Mitigations include using either dithering or black-white mode in the ebc driver, or compiling Xournal++ with https://gitlab.com/hrdl/pinenote-shared/-/blob/main/patches/xournalpp/0001-Disable-anti-aliasing-and-use-NEAREST-interpolation-.patch.

=== Obsidian ===
Works well, EInk-Theme can be found [https://github.com/MichiMolle/obsidian-eink here].

== Web Browsing ==

=== Firefox ===
Pretty good experience! Enabling GPU acceleration is helpful.

==== GPU Acceleration in Firefox ====
See [https://github.com/0cc4m/pinenote-misc#firefox-hardware-acceleration 0ccam's notes here].

== "Cloud" ==
=== syncthing ===
High contrast theme can be found [https://github.com/MichiMolle/syncthing-eink here].

[[Category:PineNote]]

PineNote

2023-02-04T12:09:46Z

Mweigand: /* PineNote Developer kit version */

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for the PineNote and [[Quartz64|Quartz64 Model A]]:
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct download] from ''pine64.org'' (32.67GB, MD5 of the TAR-GZip file ''24554419aec29700add97167a3a4c9ed'')
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz Mirror by mwfc]
** An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

Android 11 e-ink SDK for the PineNote and [[Quartz64|Quartz64 Model A]. This is the Android SDK build for 10.3" eink panels on Quartz64 Model A.

Download:
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct download] from ''pine64.org'' (72.88GB, MD5 of the TAR-GZip file ''293a550584298de4fb95ceae18103672'')
* [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz Mirror by mwfc]
* An unofficial torrent download provided by a community member of the BSP Linux and Android SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).
* Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]

Notes:
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accessory Mode (''DAM'') without having to open up the device.
The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

In case you loose your dongle, you can rebuild one using a USB-C Breakout board.

It is also relatively easy to build your own UART interface with a USB-C breakout board (for example https://www.ebay.com/itm/275407037613), two resistors and a 3.3V USB serial adapter. It is basically just two 1K pull up resistors (R3, R4), the data sheet values of 10K isn't whats on the real hardware, see the [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf schematic]. The pull ups enable the serial output on SBU1 and SBU2 you can use with any 3.3V USB serial adapter.

The UART dongle is not necessary to flash the PineNote, but is essential if something goes wrong to fix it without having to open the case.

You can flash premade images with the following links:
* https://github.com/m-weigand/pinenote_uboot_patching_dorians_backup (Note: this creates a U-Boot image to flash, do not worry about idblock.bin on the instructions for the next link)
* https://github.com/m-weigand/pinenote-debian-recipes/releases/

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
* Version v1.2 is the PineNote production version that was sold through the Pines64 store
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file] Note: When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2023-01-27T13:52:19Z

Mweigand: sort SDK/BSP downloads into the software section

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]
* BSP Linux SDK version 4.19 for PineNote and Quart64 model A SBC
** [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67GB
** An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

Android 11 e-ink SDK for PineNote and Quart64 model A SBC
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK
** An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accesory Mode (DAM) without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
* Version v1.2 is the PineNote production version that was sold through the Pines64 store
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2023-01-27T13:49:16Z

Mweigand: Try to restructure the PineNote Software section

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[PineNote Development/Flashing]] for general flashing instructions of data to the PineNote
* [[PineNote Development/TODOs]]

==== Linux Kernel ====

* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.
* [[PineNote Development/Building Kernel]]

==== User Space ====

* [[PineNote Development/Booting Linux]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

==== Android ====

==== Related ====
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accesory Mode (DAM) without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
* Version v1.2 is the PineNote production version that was sold through the Pines64 store
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== BSP Linux SDK ==

BSP Linux SDK version 4.19 for PineNote and Quart64 model A SBC
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67GB

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

== Android SDK ==

Android 11 e-ink SDK for PineNote and Quart64 model A SBC
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2023-01-27T13:18:22Z

Mweigand: delete duplicate information

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

Flashing, compiling and similar:
* [[PineNote Development/Flashing]]
* [[PineNote Development/Booting Linux]]
* [[PineNote Development/Building Kernel]]
* [[PineNote Development/TODOs]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

Related:
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accesory Mode (DAM) without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
* Version v1.2 is the PineNote production version that was sold through the Pines64 store
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== BSP Linux SDK ==

BSP Linux SDK version 4.19 for PineNote and Quart64 model A SBC
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67GB

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

== Android SDK ==

Android 11 e-ink SDK for PineNote and Quart64 model A SBC
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Development/Flashing

2023-01-27T13:17:31Z

Mweigand: reformulate entry text

{{Under construction}}

{{Info|These instructions are directed towards experienced developers only!}}

Currently, software can be flashed using rkdeveloptool or from the factory Android installation (UART shell, adb, or fastboot).

== Backup ==

{{Info|A backup of the content of the internal eMMC before anything gets messed is '''mandatory'''.}}

Especially the ''waveform'' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like U-Boot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large ''userdata'' partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched U-Boo for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

Build rkdeveloptool:

git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..

Download mode
Enter the download mode by placing the pen as pictured below. A magnet placed where the pen's cap is should also work (haven't tried). I guess the dot on the case also indicates the position of the sensor.

placing pen on the back

<code>lsusb</code> should now recognize the PineNote as:

2207:350a Fuzhou Rockchip Electronics Company USB download gadget

List partitions:

> rkdeveloptool list-partitions
# LBA start (sectors) LBA end (sectors) Size (bytes) Name
00 16384 24575 4194304 uboot
01 24576 32767 4194304 trust
02 32768 36863 2097152 waveform
03 36864 45055 4194304 misc
04 45056 53247 4194304 dtbo
05 53248 55295 1048576 vbmeta
06 55296 137215 41943040 boot
07 137216 145407 4194304 security
08 145408 407551 134217728 recovery
09 407552 1193983 402653184 backup
10 1193984 3291135 1073741824 cache
11 3291136 3323903 16777216 metadata
12 3323904 9697279 3263168512 super
13 9697280 9730047 16777216 logo
14 9730048 9861119 67108864 device
15 9861120 241827775 118766927872 userdata

{{Warning|this process is very new! Proceed at your own risk.}}

See [https://github.com/m-weigand/pinenote-debian-recipes/releases/tag/v0.1 instructions on this artifact]. It will instruct you on extracting the rootfs into an empty ext4 partition. This can be done from Linux or Android. Further instructions on building your own rootfs [https://github.com/m-weigand/pinenote-debian-recipes can be found here].

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk.

It also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
TODO

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using ''dd''.

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the eMMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the current version (current as of 2022-01-02), there might have to be made a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that ''Loader'' here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays ''Maskrom'' (not ''Loader'') from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ''ctrl-c'' (while attached using an UART dongle)
# While in u-boot use the command <code>rockusb 0 mmc 0</code> to start Rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between U-Boot and Rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

./rkdeveloptool list

It should output something like "''DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom''". If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:

./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin

This should output "''Downloading bootloader succeeded''".

We can now verify that this worked using e.g. the "read flash info" command:

./rkdeveloptool read-flash-info

{{Note|'''TODO:''' Section needs to be finished}}

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for [[PineNote Development/Flashing#Creating a mainline boot image|Creating a mainline boot image]], but instead of flashing it with ''rkdeveloptool'', use ''fastboot''. You can enter fastboot in either of two ways:

* Use "reboot bootloader" from adb or a UART console or
* get a U-Boot prompt and run <code>fastboot usb 0</code>.

[[Category:PineNote]]

PineNote

2023-01-27T13:11:31Z

Mweigand: Minor reformulation of */ Software releases */

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
While there are no robust and tested operating system releases for the PineNote available at this time, various linux distributions can be installed on the PineNote, with various degrees of working functionality.
Operating system software releases, or efforts to create them, can be found in the [[PineNote Software Releases]] section. Please join the development effort and help creating one.

== Installation instructions ==

The device can be flashed using the following instructions: [[PineNote Development/Flashing]]

{{Info|These instructions are directed towards experienced developers only!}}

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

Flashing, compiling and similar:
* [[PineNote Development/Flashing]]
* [[PineNote Development/Booting Linux]]
* [[PineNote Development/Building Kernel]]
* [[PineNote Development/TODOs]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

Related:
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accesory Mode (DAM) without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
* Version v1.2 is the PineNote production version that was sold through the Pines64 store
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== BSP Linux SDK ==

BSP Linux SDK version 4.19 for PineNote and Quart64 model A SBC
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67GB

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

== Android SDK ==

Android 11 e-ink SDK for PineNote and Quart64 model A SBC
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote

2023-01-27T13:04:20Z

Mweigand: /* PineNote Information, Schematics, and Certifications */

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
There are no releases available at the current time.

Please join the development effort and help creating one.

The software releases can be found here in the future: [[PineNote Software Releases]]

== Installation instructions ==

The device can be flashed using the following instructions: [[PineNote Development/Flashing]]

{{Info|These instructions are directed towards experienced developers only!}}

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

Flashing, compiling and similar:
* [[PineNote Development/Flashing]]
* [[PineNote Development/Booting Linux]]
* [[PineNote Development/Building Kernel]]
* [[PineNote Development/TODOs]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

Related:
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accesory Mode (DAM) without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==

=== PineNote Developer kit version ===
* Version v1.2 is the PineNote production version that was sold through the Pines64 store
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.

* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== BSP Linux SDK ==

BSP Linux SDK version 4.19 for PineNote and Quart64 model A SBC
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67GB

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

== Android SDK ==

Android 11 e-ink SDK for PineNote and Quart64 model A SBC
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Software Releases

2023-01-17T08:50:46Z

Mweigand: Update Debian section of the software release section

This page contains a list of all available operating systems for the [[PineNote]] in alphabetical order.

== Alpine ==

See https://github.com/DorianRudolph/pinenotes#alpine

== Arch Linux ==

See https://github.com/DorianRudolph/pinenotes#arch-linux

== Debian ==

* A full GNOME-enabled rootfs/disc image is provided under [https://github.com/m-weigand/pinenote-debian-recipes/releases m-weigand/pinenote-debian-recipes/releases]. This image can be flashed using rkdeveloptool.
{{Info|Check the [https://github.com/m-weigand/pinenote-debian-recipes/tree/dev dev] branch and github actions artifacts (possibly requires github login) for builds newer than the latest release.}}
* A Debian-based minimalistic rootfs/disc image can be built using <code>debos</code> using the work from [https://salsa.debian.org/eugenrh Eugen Răhăian]. The GNOME image above is building on this work.

== postmarketOS ==

See https://wiki.postmarketos.org/wiki/PINE64_PineNote_(pine64-pinenote)

[[Category:PineNote]]

PineNote

2023-01-17T08:47:54Z

Mweigand: fix link to software releases

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC. In the [[PineNote_Development#Kernel_modules_/_mainlining_status|PineNote development]] wiki page you'll find the items specific for the PineNote.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Software_Releases|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Software releases ==
There are no releases available at the current time.

Please join the development effort and help creating one.

The software releases can be found here in the future: [[PineNote Software Releases]]

== Installation instructions ==

The device can be flashed using the following instructions: [[PineNote Development/Flashing]]

{{Info|These instructions are directed towards experienced developers only!}}

== Development efforts ==

The following page discusses the development efforts for the PineNote:

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

Flashing, compiling and similar:
* [[PineNote Development/Flashing]]
* [[PineNote Development/Booting Linux]]
* [[PineNote Development/Building Kernel]]
* [[PineNote Development/TODOs]]

For tweaks and tricks see:
* [[PineNote Development/Software Tweaks]]

For app development see:
* [[PineNote Development/Apps]]

Related:
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.

=== Hardware ===

This section includes discussions and their results regarding hardware changes and debugging of the PineNote.

==== Resolved issues ====

The following topics have resolved:

* [[PineNote/Hardware Changes/Closed Case UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved issues ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== UART Dongle ====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port via USB-C Debug Accesory Mode (DAM) without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==
* PineNote Developer kit version
* The v1.2 is the PineNote production schematic.
* When building USB-C console breakout board, please be aware 10k CC pin pull-up is too weak to pull CC to logically high level. Replacing it to lower resistance, such as 1k is recommended.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== BSP Linux SDK ==

BSP Linux SDK version 4.19 for PineNote and Quart64 model A SBC
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67GB

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

== Android SDK ==

Android 11 e-ink SDK for PineNote and Quart64 model A SBC
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

An unofficial torrent download provided by a community member of both SDKs can be found [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent here] (100GB).

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Development/Apps

2023-01-17T08:39:06Z

Mweigand: Slight restructuring of the Apps page; add WinkShell link

= Development =

Here are some resources I have found helpful in learning to develop on embedded Linux devices:
* Great YouTube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

Emulator recommendation for developing and testing PineNote apps: https://github.com/michaelshiel/picom-epaper

The PineNote is a specialized device, mainly due to the eink display having unique display and refresh characteristics.
Finding and configuring apps that work well sometimes requires a lot of tweaking and a lot exploring, especially for
applications containing fast screen updates and animations, as well as depend on a lot of colours.

[https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] showing the performance of a few applications.

= Desktop Environments =

=== Sway ===

* [https://github.com/hmpthcs/WinkShell WinkShell] "Collected applications, configurations and scripts for using a wlroots-based compositor with an EPD (aka e-ink display). Currently supports Sway only."

* [https://github.com/0cc4m/pinenote-misc/blob/main/sway/config/sway/config 0cc4m's config]

==== Getting touch + pen working on sway ====

If you notice that touching the screen works, but when you use the pen the mouse coordinates are inverted, don't worry! We can fix it! Set <code>rockchip_ebc.panel_reflection=0</code> on boot (see [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Configuring_the_driver this page] for more info). Add the following line to your sway config:
<pre>
# This line rotates the mouse input by 180 degrees. See https://wayland.freedesktop.org/libinput/doc/1.11.3/absolute_axes.html
input "type:table_tool" calibration_matrix -1 0 1 0 -1 1
</pre>

=== Gnome ===
[https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome Maximilian's Config]

{{info|You may need to compile a [https://github.com/m-weigand/mw_pinenote_misc/blob/main/compile_mutter.sh modified mutter] as well.}}

= Application support on the PineNote =

== Notetaking ==

=== xournal++ ===
Works well, writing is pretty quick.

=== Obsidian ===
Works well, EInk-Theme can be found [https://github.com/MichiMolle/obsidian-eink here].

== Web Browsing ==

=== Firefox ===
Pretty good experience! Enabling GPU acceleration is helpful.

==== GPU Acceleration in Firefox ====
See [https://github.com/0cc4m/pinenote-misc#firefox-hardware-acceleration 0ccam's notes here].

[[Category:PineNote]]

PineNote Development

2023-01-12T08:57:24Z

Mweigand: add rockchip_sip to required kernel modules

This article seeks to provide general development information for the [[PineNote]]. If you are new and down to try a new installation process, the easiest way to get linux is likely to [https://wiki.pine64.org/wiki/PineNote_Development/Installing_Debian install Debian] -- NOTE THAT THIS INSTALLATION PROCESS IS VERY NEW. While many people have been using the kernel that will be installed safely at this point, the instructions for installing Debian via rootfs are very new. Take backups!

The more stable recommended approach is described below:

Start with [https://github.com/DorianRudolph/pinenotes Dorian's guide] which will guide you through getting Arch installed. For instructions on building the latest kernel, see [[PineNote Development/Building Kernel]]. For helpful configurations, see [[PineNote Development/Apps]]. For ways to pitch in, see [[PineNote Development/TODOs]]. To boot Linux by default instead of Android, see [[PineNote Development/Booting Linux]]. [https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] of a user running Manjaro and some apps on their PineNote on 9/10/2022.

= Overview =

== Kernel modules / mainlining status ==

WORK IN PROGRESS !

The following table aims to provide a list of kernel modules required for running the PineNote.
It also aims at listing repositories of work in progress.
While some overlap with the Quartz64 module list ([[Quartz64_Development#Upstreaming_Status]])
is expected, only modules relevant to the PineNote hardware should be listed here.

{|class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
| Suspend mode driver
| colspan="2" style="text-align:center;"|tbd
|<code>rockchip-sip</code>
|
|-
| Touchscreen
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>cyttsp5</code>
| As of 6.2-rc1[https://git.kernel.org/linus/5b0c03e24a061f9c9e8b28fa157b80990c559a37]
|-
| Digitizer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>i2c_hid_of</code>
|
|-
| Pen BLE Buttons
| colspan="2" style="text-align:center;"|tbd
| <code>ws8100-pen</code>
|
|-
| EBC Display controller
| colspan="2" style="text-align:center;"|tbd
| <code>rockchip_ebc</code>
|
|-
| EBC PMic
| colspan="2" style="text-align:center;"|tbd
| <code>tps65185</code>
|
|-
| LED backlight driver
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>lm3630a</code>
|
|-
| Accelerometer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>st-accel-i2c</code> (silan,sc7a20)
| As of 5.18-rc1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc6ce5ac2c998d7e869d7289736e0097ce7d2ad1]
|-
| Rastergraphics unit RGA2e
| colspan="2" style="text-align:center;"|tbd
| <code>rga</code> (v4l2 mem2mem driver)
|
|-
| Mali GPU
| style="background:LightYellow; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>panfrost</code>
| As of 5.18 [https://git.kernel.org/linus/810028668c6d9da25664195d6b906c98a8169f72] this got added to the <code>.dtsi</code> file, but it's status is disabled.
I haven't seen the <code>gpu</code> node getting enabled in the <code>.dts</code> for PineNote (yet)?
|-
| Wifi/BT
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>brcmfmac</code>
|
|}

==== Development work ====

* tps65185: driver developed here: [https://github.com/smaeul/linux/tree/rk35/tps65185], small tweaks to resume behaviour added on top here: [https://github.com/m-weigand/linux/commits/mw/rk35/tps65185]
* RGA: WIP patches for activation on the Pinenote/dithering/Y4-conversion can be found here: [https://github.com/m-weigand/linux/commits/mw/rk35/rk356x-rga]. Note that the rga2e in the rk3566 only works for RAM <= 4 G!). Simple demo program found here: [https://github.com/m-weigand/rga-v4l2-demo]
* The rockchip-sip driver required for suspend/resume is currently only hacked-in [https://github.com/smaeul/linux/commit/72127ca2806623a9de52cc1de39b06a38a22fe48]

= More Information =
== High-level developer new to embedded linux? ==
Here are some resources I have found helpful in learning to develop on embedded linux devices:
* Great youtube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

== Notes Written by Some Developers ==

* https://github.com/m-weigand/mw_pinenote_misc (Not super legible "notes", but very helpful repo with patches, videos, etc)
** specifically see this section for helpful install/configure scripts: https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#compiling.
* https://github.com/0cc4m/pinenote-misc
** patch for enabling gpu: https://github.com/0cc4m/pinenote-misc/blob/main/mesa-archlinux-arm/mesa/rockchip_ebc.patch
** prebuilt pkg's: https://github.com/0cc4m/pinenote-misc/releases
* https://pwarren.id.au/pinenote/build_notes.txt
* https://github.com/DorianRudolph/pinenotes
* https://github.com/tpwrules/nixos-pinenote

== Alternative to patching of mesa ==
Mesa needs to be patched to add the driver entry point. The alternative to this, is the renaming of the ebc driver to an existing mesa driver entry point. A good existing name can be "repaper". To change the driver name, edit in the kernel tree the following files: 
- replace "rockchip-ebc" with "repaper" in the two places in the file: drivers/gpu/drm/rockchip/rockchip_ebc.c 
- preventive, replace "repaper" with "repaper-disabled" in the two places in the file: drivers/gpu/drm/tiny/repaper.c 

== Building the most recent kernel ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel here].

== Video of Factory Android OS ==

[https://www.youtube.com/watch?v=DWuTGgQHw98 PineNote Developer Edition w/Tech Demo Android OS (Video Only)]

Informal walkthrough of the factory Android installation on the PineNote Developer Edition, recorded by a community member (Apr 2022). This is useful to look back at the original OS after erasing it from your device, or to get some additional detail before your device arrives.

The video also includes a chapter at the end showing [https://www.youtube.com/watch?v=DWuTGgQHw98&t=802s how to enable Android Debug Bridge (`adb`) over USB]. Once enabled, keep the device powered and connect a USB cable directly to the PineNote (i.e. no UART breakout) to a computer running `adb`.

== Emulator for Developing/Testing Pinenote Apps ==
https://github.com/michaelshiel/picom-epaper

= Flashing Software =
Currently, the only ways to flash software are from the factory Android installation (UART shell, adb, or fastboot) or by using rkdeveloptool.

== Backup of the content of the internal MMC before you mess anything up ==
Especially the '''waveform''' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like uboot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large userdata partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched uboot for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk

I also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
For any one knowing how and with which caveats: Write ME

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using dd

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the MMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the version I cloned (current as of 2022-01-02), I had to make a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that "Loader" here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays "Maskrom" [not "Loader"] from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right, and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ctrl-c (while attached using an UART dongle)
# While in u-boot use the command "rockusb 0 mmc 0" to start rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between u-boot and rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

<pre>
./rkdeveloptool list
</pre>

It should output something like <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom</code>. If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:
<pre>
./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin
</pre>

This should output <code>Downloading bootloader succeeded.</code>.

We can now verify that this worked using e.g. the "read flash info" command:

<pre>
./rkdeveloptool read-flash-info
</pre>

'''TODO:''' finish this section

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for "Creating a mainline boot.img", but instead of flashing it with rkdeveloptool, use fastboot. You can enter fastboot in either of two ways:

# Use "reboot bootloader" from adb or a UART console.
# Get a U-Boot prompt and run <code>fastboot usb 0</code>.

= Mainline development =

== Status ==

Some work happening here: https://gitlab.com/calebccff/linux, the idea is to import the parts of the eink/ebc drivers which are open source and use the downstream u-boot framebuffer driver as a reference to create a basic framebuffer driver.

Currently mainline struggles to boot due to weird issues while probing fixed regulators (?). It also fails to detect eMMC.

Further work is being done here: https://github.com/smaeul/linux/commits/rk356x-ebc-dev. This has a complete device tree, with working eMMC. Pen input also works out of the box. Wi-Fi and BT work with firmware copied from the factory Android image.

== How to boot mainline ==

UART is currently REQUIRED for this to work! We depend on u-boot falling back to console. Once we have a prebuilt u-boot which will use extlinux by default, UART won't be needed anymore.

You can compile a u-boot that uses extlinux by default by following the instructions [https://github.com/JoshuaMulliken/pinenote_uboot/blob/aa9ecbd3d3e716f163f5a900824630f24e9f04ba/README.md#changing-default-boot-order here].

=== Getting to a U-Boot prompt ===

You can get to a U-Boot prompt by:

# Holding Ctrl-C while the display panel initializes.
# Wiping the "boot" partition.

=== Using sysboot ===

<code>extlinux.conf</code> should have the following contents:

<pre>
timeout 10
default MAINLINE
menu title boot prev kernel

label MAINLINE
kernel /vmlinuz
fdt /rk3566-pinenote.dtb
initrd /initramfs
append earlycon console=tty0 console=ttyS2,1500000n8 fw_devlink=off PMOS_NO_OUTPUT_REDIRECT
</pre>

At the u-boot console, run the following command to boot your mainline kernel:

<pre>
sysboot ${devtype} ${devnum}:9 any ${scriptaddr} extlinux.conf
</pre>

=== Booting with individual commands ===

Booting with individual commands can be useful when you need to temporarily add some kernel command line arguments. Use these or similar commands at the U-Boot shell:

load mmc 0:b ${kernel_addr_r} boot/Image
load mmc 0:b ${fdt_addr_r} boot/rk3566-pinenote.dtb
setenv bootargs ignore_loglevel root=/dev/mmcblk0p11 rootwait init=/bin/bash
booti ${kernel_addr_r} - ${fdt_addr_r}

== Configuration ==

=== Firmware for WiFi & Bluetooth and Waveform data ===

==== Using Maximilian's Debian image ====
If the Android partition (super) and waveform partition (waveform) is left intact the image extracts the WiFi, BT driver and waveform from the partitions on first run.

For instance if you repartitions the userdata partition and installs the image there.

==== Getting it from the Android install manually ====
Copy WiFi/BT firmware from Android:
mkdir -p /cache/lib/firmware/brcm
cp /vendor/etc/firmware/fw_bcm43455c0_ag_cy.bin /cache/lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /vendor/etc/firmware/nvram_ap6255_cy.txt /cache/lib/firmware/brcm/brcmfmac43455-sdio.txt
cp /cache/lib/firmware/BCM4345C0.hcd /cache/lib/firmware/brcm/BCM4345C0.hcd

Copy waveform partition (via previously dumped file):
adb root
adb push waveform.img /cache/lib/firmware/waveform.bin

Or via dd within Linux:
dd if=/dev/mmcblk0p3 of=/lib/firmware/waveform.bin bs=1k count=2048

==== Getting the Wifi and Bluetooth driver blobs from "other" sources ====
===== WiFi =====
The WiFi firmware .bin blob can be obtained by installing the Debian package firmware-brcm80211 (in the non-free section)

The WiFi brcmfmac43455-sdio.txt file can according to Eugen be sourced from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm/brcmfmac43455-sdio.AW-CM256SM.txt needs a renaming when copying it to /lib/firmware/brcm/brcmfmac43455-sdio.txt)

''The content of the upstream .txt is different than the Android configuration, but is supposed to work.''

As you don't have WiFi yet you need to get the firmware-brcm80211*.deb and brcmfmac43455-sdio.txt file on the PineNote by other means, for instance using an USB stick

===== Bluetooth =====

Once you have WiFi working you can get BCM4345C0.hcd by installing the bluez-firmware
sudo apt install bluez-firmware

=== Configuring the E-ink refresh mode ===
https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches contains information on how/where to write in /sys to alter the refresh mode

https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension contains the gnome extension used in Maximilian image

=== Touchscreen and Pen In X.org ===

By default the pen config is flipped 180° (which makes it unusable) and the touchscreen doesn't work. Placing the following config in <code>/etc/X11/xorg.conf.d/50-touchscreen.conf</code> will fix both problems:

<pre>
Section "InputClass"
Identifier "evdev touchscreen"
MatchProduct "tt21000"
MatchIsTouchscreen "on"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "RotateTouch"
MatchProduct "w9013"
Option "TransformationMatrix" "-1 0 1 0 -1 1 0 0 1"
EndSection
</pre>

PineNote Development

2023-01-11T09:31:28Z

Mweigand: Add links to work in progress development of kernel modules

This article seeks to provide general development information for the [[PineNote]]. If you are new and down to try a new installation process, the easiest way to get linux is likely to [https://wiki.pine64.org/wiki/PineNote_Development/Installing_Debian install Debian] -- NOTE THAT THIS INSTALLATION PROCESS IS VERY NEW. While many people have been using the kernel that will be installed safely at this point, the instructions for installing Debian via rootfs are very new. Take backups!

The more stable recommended approach is described below:

Start with [https://github.com/DorianRudolph/pinenotes Dorian's guide] which will guide you through getting Arch installed. For instructions on building the latest kernel, see [[PineNote Development/Building Kernel]]. For helpful configurations, see [[PineNote Development/Apps]]. For ways to pitch in, see [[PineNote Development/TODOs]]. To boot Linux by default instead of Android, see [[PineNote Development/Booting Linux]]. [https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] of a user running Manjaro and some apps on their PineNote on 9/10/2022.

= Overview =

== Kernel modules / mainlining status ==

WORK IN PROGRESS !

The following table aims to provide a list of kernel modules required for running the PineNote.
It also aims at listing repositories of work in progress.
While some overlap with the Quartz64 module list ([[Quartz64_Development#Upstreaming_Status]])
is expected, only modules relevant to the PineNote hardware should be listed here.

{|class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
| Touchscreen
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>cyttsp5</code>
| As of 6.2-rc1[https://git.kernel.org/linus/5b0c03e24a061f9c9e8b28fa157b80990c559a37]
|-
| Digitizer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>i2c_hid_of</code>
|
|-
| Pen BLE Buttons
| colspan="2" style="text-align:center;"|tbd
| <code>ws8100-pen</code>
|
|-
| EBC Display controller
| colspan="2" style="text-align:center;"|tbd
| <code>rockchip_ebc</code>
|
|-
| EBC PMic
| colspan="2" style="text-align:center;"|tbd
| <code>tps65185</code>
|
|-
| LED backlight driver
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>lm3630a</code>
|
|-
| Accelerometer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>st-accel-i2c</code> (silan,sc7a20)
| As of 5.18-rc1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc6ce5ac2c998d7e869d7289736e0097ce7d2ad1]
|-
| Rastergraphics unit RGA2e
| colspan="2" style="text-align:center;"|tbd
| <code>rga</code> (v4l2 mem2mem driver)
|
|-
| Mali GPU
| style="background:LightYellow; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>panfrost</code>
| As of 5.18 [https://git.kernel.org/linus/810028668c6d9da25664195d6b906c98a8169f72] this got added to the <code>.dtsi</code> file, but it's status is disabled.
I haven't seen the <code>gpu</code> node getting enabled in the <code>.dts</code> for PineNote (yet)?
|-
| Wifi/BT
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>brcmfmac</code>
|
|}

==== Development work ====

* tps65185: driver developed here: [https://github.com/smaeul/linux/tree/rk35/tps65185], small tweaks to resume behaviour added on top here: [https://github.com/m-weigand/linux/commits/mw/rk35/tps65185]
* RGA: WIP patches for activation on the Pinenote/dithering/Y4-conversion can be found here: [https://github.com/m-weigand/linux/commits/mw/rk35/rk356x-rga]. Note that the rga2e in the rk3566 only works for RAM <= 4 G!). Simple demo program found here: [https://github.com/m-weigand/rga-v4l2-demo]

= More Information =
== High-level developer new to embedded linux? ==
Here are some resources I have found helpful in learning to develop on embedded linux devices:
* Great youtube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

== Notes Written by Some Developers ==

* https://github.com/m-weigand/mw_pinenote_misc (Not super legible "notes", but very helpful repo with patches, videos, etc)
** specifically see this section for helpful install/configure scripts: https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#compiling.
* https://github.com/0cc4m/pinenote-misc
** patch for enabling gpu: https://github.com/0cc4m/pinenote-misc/blob/main/mesa-archlinux-arm/mesa/rockchip_ebc.patch
** prebuilt pkg's: https://github.com/0cc4m/pinenote-misc/releases
* https://pwarren.id.au/pinenote/build_notes.txt
* https://github.com/DorianRudolph/pinenotes
* https://github.com/tpwrules/nixos-pinenote

== Alternative to patching of mesa ==
Mesa needs to be patched to add the driver entry point. The alternative to this, is the renaming of the ebc driver to an existing mesa driver entry point. A good existing name can be "repaper". To change the driver name, edit in the kernel tree the following files: 
- replace "rockchip-ebc" with "repaper" in the two places in the file: drivers/gpu/drm/rockchip/rockchip_ebc.c 
- preventive, replace "repaper" with "repaper-disabled" in the two places in the file: drivers/gpu/drm/tiny/repaper.c 

== Building the most recent kernel ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel here].

== Video of Factory Android OS ==

[https://www.youtube.com/watch?v=DWuTGgQHw98 PineNote Developer Edition w/Tech Demo Android OS (Video Only)]

Informal walkthrough of the factory Android installation on the PineNote Developer Edition, recorded by a community member (Apr 2022). This is useful to look back at the original OS after erasing it from your device, or to get some additional detail before your device arrives.

The video also includes a chapter at the end showing [https://www.youtube.com/watch?v=DWuTGgQHw98&t=802s how to enable Android Debug Bridge (`adb`) over USB]. Once enabled, keep the device powered and connect a USB cable directly to the PineNote (i.e. no UART breakout) to a computer running `adb`.

== Emulator for Developing/Testing Pinenote Apps ==
https://github.com/michaelshiel/picom-epaper

= Flashing Software =
Currently, the only ways to flash software are from the factory Android installation (UART shell, adb, or fastboot) or by using rkdeveloptool.

== Backup of the content of the internal MMC before you mess anything up ==
Especially the '''waveform''' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like uboot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large userdata partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched uboot for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk

I also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
For any one knowing how and with which caveats: Write ME

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using dd

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the MMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the version I cloned (current as of 2022-01-02), I had to make a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that "Loader" here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays "Maskrom" [not "Loader"] from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right, and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ctrl-c (while attached using an UART dongle)
# While in u-boot use the command "rockusb 0 mmc 0" to start rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between u-boot and rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

<pre>
./rkdeveloptool list
</pre>

It should output something like <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom</code>. If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:
<pre>
./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin
</pre>

This should output <code>Downloading bootloader succeeded.</code>.

We can now verify that this worked using e.g. the "read flash info" command:

<pre>
./rkdeveloptool read-flash-info
</pre>

'''TODO:''' finish this section

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for "Creating a mainline boot.img", but instead of flashing it with rkdeveloptool, use fastboot. You can enter fastboot in either of two ways:

# Use "reboot bootloader" from adb or a UART console.
# Get a U-Boot prompt and run <code>fastboot usb 0</code>.

= Mainline development =

== Status ==

Some work happening here: https://gitlab.com/calebccff/linux, the idea is to import the parts of the eink/ebc drivers which are open source and use the downstream u-boot framebuffer driver as a reference to create a basic framebuffer driver.

Currently mainline struggles to boot due to weird issues while probing fixed regulators (?). It also fails to detect eMMC.

Further work is being done here: https://github.com/smaeul/linux/commits/rk356x-ebc-dev. This has a complete device tree, with working eMMC. Pen input also works out of the box. Wi-Fi and BT work with firmware copied from the factory Android image.

== How to boot mainline ==

UART is currently REQUIRED for this to work! We depend on u-boot falling back to console. Once we have a prebuilt u-boot which will use extlinux by default, UART won't be needed anymore.

You can compile a u-boot that uses extlinux by default by following the instructions [https://github.com/JoshuaMulliken/pinenote_uboot/blob/aa9ecbd3d3e716f163f5a900824630f24e9f04ba/README.md#changing-default-boot-order here].

=== Getting to a U-Boot prompt ===

You can get to a U-Boot prompt by:

# Holding Ctrl-C while the display panel initializes.
# Wiping the "boot" partition.

=== Using sysboot ===

<code>extlinux.conf</code> should have the following contents:

<pre>
timeout 10
default MAINLINE
menu title boot prev kernel

label MAINLINE
kernel /vmlinuz
fdt /rk3566-pinenote.dtb
initrd /initramfs
append earlycon console=tty0 console=ttyS2,1500000n8 fw_devlink=off PMOS_NO_OUTPUT_REDIRECT
</pre>

At the u-boot console, run the following command to boot your mainline kernel:

<pre>
sysboot ${devtype} ${devnum}:9 any ${scriptaddr} extlinux.conf
</pre>

=== Booting with individual commands ===

Booting with individual commands can be useful when you need to temporarily add some kernel command line arguments. Use these or similar commands at the U-Boot shell:

load mmc 0:b ${kernel_addr_r} boot/Image
load mmc 0:b ${fdt_addr_r} boot/rk3566-pinenote.dtb
setenv bootargs ignore_loglevel root=/dev/mmcblk0p11 rootwait init=/bin/bash
booti ${kernel_addr_r} - ${fdt_addr_r}

== Configuration ==

=== Firmware for WiFi & Bluetooth and Waveform data ===

==== Using Maximilian's Debian image ====
If the Android partition (super) and waveform partition (waveform) is left intact the image extracts the WiFi, BT driver and waveform from the partitions on first run.

For instance if you repartitions the userdata partition and installs the image there.

==== Getting it from the Android install manually ====
Copy WiFi/BT firmware from Android:
mkdir -p /cache/lib/firmware/brcm
cp /vendor/etc/firmware/fw_bcm43455c0_ag_cy.bin /cache/lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /vendor/etc/firmware/nvram_ap6255_cy.txt /cache/lib/firmware/brcm/brcmfmac43455-sdio.txt
cp /cache/lib/firmware/BCM4345C0.hcd /cache/lib/firmware/brcm/BCM4345C0.hcd

Copy waveform partition (via previously dumped file):
adb root
adb push waveform.img /cache/lib/firmware/waveform.bin

Or via dd within Linux:
dd if=/dev/mmcblk0p3 of=/lib/firmware/waveform.bin bs=1k count=2048

==== Getting the Wifi and Bluetooth driver blobs from "other" sources ====
===== WiFi =====
The WiFi firmware .bin blob can be obtained by installing the Debian package firmware-brcm80211 (in the non-free section)

The WiFi brcmfmac43455-sdio.txt file can according to Eugen be sourced from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm/brcmfmac43455-sdio.AW-CM256SM.txt needs a renaming when copying it to /lib/firmware/brcm/brcmfmac43455-sdio.txt)

''The content of the upstream .txt is different than the Android configuration, but is supposed to work.''

As you don't have WiFi yet you need to get the firmware-brcm80211*.deb and brcmfmac43455-sdio.txt file on the PineNote by other means, for instance using an USB stick

===== Bluetooth =====

Once you have WiFi working you can get BCM4345C0.hcd by installing the bluez-firmware
sudo apt install bluez-firmware

=== Configuring the E-ink refresh mode ===
https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches contains information on how/where to write in /sys to alter the refresh mode

https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension contains the gnome extension used in Maximilian image

=== Touchscreen and Pen In X.org ===

By default the pen config is flipped 180° (which makes it unusable) and the touchscreen doesn't work. Placing the following config in <code>/etc/X11/xorg.conf.d/50-touchscreen.conf</code> will fix both problems:

<pre>
Section "InputClass"
Identifier "evdev touchscreen"
MatchProduct "tt21000"
MatchIsTouchscreen "on"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "RotateTouch"
MatchProduct "w9013"
Option "TransformationMatrix" "-1 0 1 0 -1 1 0 0 1"
EndSection
</pre>

PineNote Development

2023-01-11T09:19:15Z

Mweigand: Update mainline status of backlight driver

This article seeks to provide general development information for the [[PineNote]]. If you are new and down to try a new installation process, the easiest way to get linux is likely to [https://wiki.pine64.org/wiki/PineNote_Development/Installing_Debian install Debian] -- NOTE THAT THIS INSTALLATION PROCESS IS VERY NEW. While many people have been using the kernel that will be installed safely at this point, the instructions for installing Debian via rootfs are very new. Take backups!

The more stable recommended approach is described below:

Start with [https://github.com/DorianRudolph/pinenotes Dorian's guide] which will guide you through getting Arch installed. For instructions on building the latest kernel, see [[PineNote Development/Building Kernel]]. For helpful configurations, see [[PineNote Development/Apps]]. For ways to pitch in, see [[PineNote Development/TODOs]]. To boot Linux by default instead of Android, see [[PineNote Development/Booting Linux]]. [https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] of a user running Manjaro and some apps on their PineNote on 9/10/2022.

= Overview =

== Kernel modules / mainlining status ==

WORK IN PROGRESS !

The following table aims to provide a list of kernel modules required for running the PineNote.
It also aims at listing repositories of work in progress.
While some overlap with the Quartz64 module list ([[Quartz64_Development#Upstreaming_Status]])
is expected, only modules relevant to the PineNote hardware should be listed here.

{|class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
| Touchscreen
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>cyttsp5</code>
| As of 6.2-rc1[https://git.kernel.org/linus/5b0c03e24a061f9c9e8b28fa157b80990c559a37]
|-
| Digitizer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>i2c_hid_of</code>
|
|-
| Pen BLE Buttons
| colspan="2" style="text-align:center;"|tbd
| <code>ws8100-pen</code>
|
|-
| EBC Display controller
| colspan="2" style="text-align:center;"|tbd
| <code>rockchip_ebc</code>
|
|-
| EBC PMic
| colspan="2" style="text-align:center;"|tbd
| <code>tps65185</code>
|
|-
| LED backlight driver
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>lm3630a</code>
|
|-
| Accelerometer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>st-accel-i2c</code> (silan,sc7a20)
| As of 5.18-rc1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc6ce5ac2c998d7e869d7289736e0097ce7d2ad1]
|-
| Rastergraphics unit RGA2e
| colspan="2" style="text-align:center;"|tbd
| <code>rga</code> (v4l2 mem2mem driver)
|
|-
| Mali GPU
| style="background:LightYellow; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>panfrost</code>
| As of 5.18 [https://git.kernel.org/linus/810028668c6d9da25664195d6b906c98a8169f72] this got added to the <code>.dtsi</code> file, but it's status is disabled.
I haven't seen the <code>gpu</code> node getting enabled in the <code>.dts</code> for PineNote (yet)?
|-
| Wifi/BT
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>brcmfmac</code>
|
|}

= More Information =
== High-level developer new to embedded linux? ==
Here are some resources I have found helpful in learning to develop on embedded linux devices:
* Great youtube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

== Notes Written by Some Developers ==

* https://github.com/m-weigand/mw_pinenote_misc (Not super legible "notes", but very helpful repo with patches, videos, etc)
** specifically see this section for helpful install/configure scripts: https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#compiling.
* https://github.com/0cc4m/pinenote-misc
** patch for enabling gpu: https://github.com/0cc4m/pinenote-misc/blob/main/mesa-archlinux-arm/mesa/rockchip_ebc.patch
** prebuilt pkg's: https://github.com/0cc4m/pinenote-misc/releases
* https://pwarren.id.au/pinenote/build_notes.txt
* https://github.com/DorianRudolph/pinenotes
* https://github.com/tpwrules/nixos-pinenote

== Alternative to patching of mesa ==
Mesa needs to be patched to add the driver entry point. The alternative to this, is the renaming of the ebc driver to an existing mesa driver entry point. A good existing name can be "repaper". To change the driver name, edit in the kernel tree the following files: 
- replace "rockchip-ebc" with "repaper" in the two places in the file: drivers/gpu/drm/rockchip/rockchip_ebc.c 
- preventive, replace "repaper" with "repaper-disabled" in the two places in the file: drivers/gpu/drm/tiny/repaper.c 

== Building the most recent kernel ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel here].

== Video of Factory Android OS ==

[https://www.youtube.com/watch?v=DWuTGgQHw98 PineNote Developer Edition w/Tech Demo Android OS (Video Only)]

Informal walkthrough of the factory Android installation on the PineNote Developer Edition, recorded by a community member (Apr 2022). This is useful to look back at the original OS after erasing it from your device, or to get some additional detail before your device arrives.

The video also includes a chapter at the end showing [https://www.youtube.com/watch?v=DWuTGgQHw98&t=802s how to enable Android Debug Bridge (`adb`) over USB]. Once enabled, keep the device powered and connect a USB cable directly to the PineNote (i.e. no UART breakout) to a computer running `adb`.

== Emulator for Developing/Testing Pinenote Apps ==
https://github.com/michaelshiel/picom-epaper

= Flashing Software =
Currently, the only ways to flash software are from the factory Android installation (UART shell, adb, or fastboot) or by using rkdeveloptool.

== Backup of the content of the internal MMC before you mess anything up ==
Especially the '''waveform''' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like uboot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large userdata partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched uboot for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk

I also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
For any one knowing how and with which caveats: Write ME

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using dd

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the MMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the version I cloned (current as of 2022-01-02), I had to make a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that "Loader" here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays "Maskrom" [not "Loader"] from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right, and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ctrl-c (while attached using an UART dongle)
# While in u-boot use the command "rockusb 0 mmc 0" to start rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between u-boot and rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

<pre>
./rkdeveloptool list
</pre>

It should output something like <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom</code>. If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:
<pre>
./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin
</pre>

This should output <code>Downloading bootloader succeeded.</code>.

We can now verify that this worked using e.g. the "read flash info" command:

<pre>
./rkdeveloptool read-flash-info
</pre>

'''TODO:''' finish this section

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for "Creating a mainline boot.img", but instead of flashing it with rkdeveloptool, use fastboot. You can enter fastboot in either of two ways:

# Use "reboot bootloader" from adb or a UART console.
# Get a U-Boot prompt and run <code>fastboot usb 0</code>.

= Mainline development =

== Status ==

Some work happening here: https://gitlab.com/calebccff/linux, the idea is to import the parts of the eink/ebc drivers which are open source and use the downstream u-boot framebuffer driver as a reference to create a basic framebuffer driver.

Currently mainline struggles to boot due to weird issues while probing fixed regulators (?). It also fails to detect eMMC.

Further work is being done here: https://github.com/smaeul/linux/commits/rk356x-ebc-dev. This has a complete device tree, with working eMMC. Pen input also works out of the box. Wi-Fi and BT work with firmware copied from the factory Android image.

== How to boot mainline ==

UART is currently REQUIRED for this to work! We depend on u-boot falling back to console. Once we have a prebuilt u-boot which will use extlinux by default, UART won't be needed anymore.

You can compile a u-boot that uses extlinux by default by following the instructions [https://github.com/JoshuaMulliken/pinenote_uboot/blob/aa9ecbd3d3e716f163f5a900824630f24e9f04ba/README.md#changing-default-boot-order here].

=== Getting to a U-Boot prompt ===

You can get to a U-Boot prompt by:

# Holding Ctrl-C while the display panel initializes.
# Wiping the "boot" partition.

=== Using sysboot ===

<code>extlinux.conf</code> should have the following contents:

<pre>
timeout 10
default MAINLINE
menu title boot prev kernel

label MAINLINE
kernel /vmlinuz
fdt /rk3566-pinenote.dtb
initrd /initramfs
append earlycon console=tty0 console=ttyS2,1500000n8 fw_devlink=off PMOS_NO_OUTPUT_REDIRECT
</pre>

At the u-boot console, run the following command to boot your mainline kernel:

<pre>
sysboot ${devtype} ${devnum}:9 any ${scriptaddr} extlinux.conf
</pre>

=== Booting with individual commands ===

Booting with individual commands can be useful when you need to temporarily add some kernel command line arguments. Use these or similar commands at the U-Boot shell:

load mmc 0:b ${kernel_addr_r} boot/Image
load mmc 0:b ${fdt_addr_r} boot/rk3566-pinenote.dtb
setenv bootargs ignore_loglevel root=/dev/mmcblk0p11 rootwait init=/bin/bash
booti ${kernel_addr_r} - ${fdt_addr_r}

== Configuration ==

=== Firmware for WiFi & Bluetooth and Waveform data ===

==== Using Maximilian's Debian image ====
If the Android partition (super) and waveform partition (waveform) is left intact the image extracts the WiFi, BT driver and waveform from the partitions on first run.

For instance if you repartitions the userdata partition and installs the image there.

==== Getting it from the Android install manually ====
Copy WiFi/BT firmware from Android:
mkdir -p /cache/lib/firmware/brcm
cp /vendor/etc/firmware/fw_bcm43455c0_ag_cy.bin /cache/lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /vendor/etc/firmware/nvram_ap6255_cy.txt /cache/lib/firmware/brcm/brcmfmac43455-sdio.txt
cp /cache/lib/firmware/BCM4345C0.hcd /cache/lib/firmware/brcm/BCM4345C0.hcd

Copy waveform partition (via previously dumped file):
adb root
adb push waveform.img /cache/lib/firmware/waveform.bin

Or via dd within Linux:
dd if=/dev/mmcblk0p3 of=/lib/firmware/waveform.bin bs=1k count=2048

==== Getting the Wifi and Bluetooth driver blobs from "other" sources ====
===== WiFi =====
The WiFi firmware .bin blob can be obtained by installing the Debian package firmware-brcm80211 (in the non-free section)

The WiFi brcmfmac43455-sdio.txt file can according to Eugen be sourced from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm/brcmfmac43455-sdio.AW-CM256SM.txt needs a renaming when copying it to /lib/firmware/brcm/brcmfmac43455-sdio.txt)

''The content of the upstream .txt is different than the Android configuration, but is supposed to work.''

As you don't have WiFi yet you need to get the firmware-brcm80211*.deb and brcmfmac43455-sdio.txt file on the PineNote by other means, for instance using an USB stick

===== Bluetooth =====

Once you have WiFi working you can get BCM4345C0.hcd by installing the bluez-firmware
sudo apt install bluez-firmware

=== Configuring the E-ink refresh mode ===
https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches contains information on how/where to write in /sys to alter the refresh mode

https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension contains the gnome extension used in Maximilian image

=== Touchscreen and Pen In X.org ===

By default the pen config is flipped 180° (which makes it unusable) and the touchscreen doesn't work. Placing the following config in <code>/etc/X11/xorg.conf.d/50-touchscreen.conf</code> will fix both problems:

<pre>
Section "InputClass"
Identifier "evdev touchscreen"
MatchProduct "tt21000"
MatchIsTouchscreen "on"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "RotateTouch"
MatchProduct "w9013"
Option "TransformationMatrix" "-1 0 1 0 -1 1 0 0 1"
EndSection
</pre>

PineNote Development

2023-01-11T09:16:14Z

Mweigand: Update mainline status of accelerometer st-accel-i2c (silan,sc7a20)

This article seeks to provide general development information for the [[PineNote]]. If you are new and down to try a new installation process, the easiest way to get linux is likely to [https://wiki.pine64.org/wiki/PineNote_Development/Installing_Debian install Debian] -- NOTE THAT THIS INSTALLATION PROCESS IS VERY NEW. While many people have been using the kernel that will be installed safely at this point, the instructions for installing Debian via rootfs are very new. Take backups!

The more stable recommended approach is described below:

Start with [https://github.com/DorianRudolph/pinenotes Dorian's guide] which will guide you through getting Arch installed. For instructions on building the latest kernel, see [[PineNote Development/Building Kernel]]. For helpful configurations, see [[PineNote Development/Apps]]. For ways to pitch in, see [[PineNote Development/TODOs]]. To boot Linux by default instead of Android, see [[PineNote Development/Booting Linux]]. [https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] of a user running Manjaro and some apps on their PineNote on 9/10/2022.

= Overview =

== Kernel modules / mainlining status ==

WORK IN PROGRESS !

The following table aims to provide a list of kernel modules required for running the PineNote.
It also aims at listing repositories of work in progress.
While some overlap with the Quartz64 module list ([[Quartz64_Development#Upstreaming_Status]])
is expected, only modules relevant to the PineNote hardware should be listed here.

{|class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
| Touchscreen
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>cyttsp5</code>
| As of 6.2-rc1[https://git.kernel.org/linus/5b0c03e24a061f9c9e8b28fa157b80990c559a37]
|-
| Digitizer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>i2c_hid_of</code>
|
|-
| Pen BLE Buttons
| colspan="2" style="text-align:center;"|tbd
| <code>ws8100-pen</code>
|
|-
| EBC Display controller
| colspan="2" style="text-align:center;"|tbd
| <code>rockchip_ebc</code>
|
|-
| EBC PMic
| colspan="2" style="text-align:center;"|tbd
| <code>tps65185</code>
|
|-
| LED backlight driver
| colspan="2" style="text-align:center;"|tbd
| <code>lm3630a</code>
|
|-
| Accelerometer
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>st-accel-i2c</code> (silan,sc7a20)
| As of 5.18-rc1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc6ce5ac2c998d7e869d7289736e0097ce7d2ad1]
|-
| Rastergraphics unit RGA2e
| colspan="2" style="text-align:center;"|tbd
| <code>rga</code> (v4l2 mem2mem driver)
|
|-
| Mali GPU
| style="background:LightYellow; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>panfrost</code>
| As of 5.18 [https://git.kernel.org/linus/810028668c6d9da25664195d6b906c98a8169f72] this got added to the <code>.dtsi</code> file, but it's status is disabled.
I haven't seen the <code>gpu</code> node getting enabled in the <code>.dts</code> for PineNote (yet)?
|-
| Wifi/BT
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>brcmfmac</code>
|
|}

= More Information =
== High-level developer new to embedded linux? ==
Here are some resources I have found helpful in learning to develop on embedded linux devices:
* Great youtube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

== Notes Written by Some Developers ==

* https://github.com/m-weigand/mw_pinenote_misc (Not super legible "notes", but very helpful repo with patches, videos, etc)
** specifically see this section for helpful install/configure scripts: https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#compiling.
* https://github.com/0cc4m/pinenote-misc
** patch for enabling gpu: https://github.com/0cc4m/pinenote-misc/blob/main/mesa-archlinux-arm/mesa/rockchip_ebc.patch
** prebuilt pkg's: https://github.com/0cc4m/pinenote-misc/releases
* https://pwarren.id.au/pinenote/build_notes.txt
* https://github.com/DorianRudolph/pinenotes
* https://github.com/tpwrules/nixos-pinenote

== Alternative to patching of mesa ==
Mesa needs to be patched to add the driver entry point. The alternative to this, is the renaming of the ebc driver to an existing mesa driver entry point. A good existing name can be "repaper". To change the driver name, edit in the kernel tree the following files: 
- replace "rockchip-ebc" with "repaper" in the two places in the file: drivers/gpu/drm/rockchip/rockchip_ebc.c 
- preventive, replace "repaper" with "repaper-disabled" in the two places in the file: drivers/gpu/drm/tiny/repaper.c 

== Building the most recent kernel ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel here].

== Video of Factory Android OS ==

[https://www.youtube.com/watch?v=DWuTGgQHw98 PineNote Developer Edition w/Tech Demo Android OS (Video Only)]

Informal walkthrough of the factory Android installation on the PineNote Developer Edition, recorded by a community member (Apr 2022). This is useful to look back at the original OS after erasing it from your device, or to get some additional detail before your device arrives.

The video also includes a chapter at the end showing [https://www.youtube.com/watch?v=DWuTGgQHw98&t=802s how to enable Android Debug Bridge (`adb`) over USB]. Once enabled, keep the device powered and connect a USB cable directly to the PineNote (i.e. no UART breakout) to a computer running `adb`.

== Emulator for Developing/Testing Pinenote Apps ==
https://github.com/michaelshiel/picom-epaper

= Flashing Software =
Currently, the only ways to flash software are from the factory Android installation (UART shell, adb, or fastboot) or by using rkdeveloptool.

== Backup of the content of the internal MMC before you mess anything up ==
Especially the '''waveform''' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like uboot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large userdata partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched uboot for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk

I also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
For any one knowing how and with which caveats: Write ME

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using dd

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the MMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the version I cloned (current as of 2022-01-02), I had to make a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that "Loader" here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays "Maskrom" [not "Loader"] from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right, and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ctrl-c (while attached using an UART dongle)
# While in u-boot use the command "rockusb 0 mmc 0" to start rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between u-boot and rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

<pre>
./rkdeveloptool list
</pre>

It should output something like <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom</code>. If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:
<pre>
./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin
</pre>

This should output <code>Downloading bootloader succeeded.</code>.

We can now verify that this worked using e.g. the "read flash info" command:

<pre>
./rkdeveloptool read-flash-info
</pre>

'''TODO:''' finish this section

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for "Creating a mainline boot.img", but instead of flashing it with rkdeveloptool, use fastboot. You can enter fastboot in either of two ways:

# Use "reboot bootloader" from adb or a UART console.
# Get a U-Boot prompt and run <code>fastboot usb 0</code>.

= Mainline development =

== Status ==

Some work happening here: https://gitlab.com/calebccff/linux, the idea is to import the parts of the eink/ebc drivers which are open source and use the downstream u-boot framebuffer driver as a reference to create a basic framebuffer driver.

Currently mainline struggles to boot due to weird issues while probing fixed regulators (?). It also fails to detect eMMC.

Further work is being done here: https://github.com/smaeul/linux/commits/rk356x-ebc-dev. This has a complete device tree, with working eMMC. Pen input also works out of the box. Wi-Fi and BT work with firmware copied from the factory Android image.

== How to boot mainline ==

UART is currently REQUIRED for this to work! We depend on u-boot falling back to console. Once we have a prebuilt u-boot which will use extlinux by default, UART won't be needed anymore.

You can compile a u-boot that uses extlinux by default by following the instructions [https://github.com/JoshuaMulliken/pinenote_uboot/blob/aa9ecbd3d3e716f163f5a900824630f24e9f04ba/README.md#changing-default-boot-order here].

=== Getting to a U-Boot prompt ===

You can get to a U-Boot prompt by:

# Holding Ctrl-C while the display panel initializes.
# Wiping the "boot" partition.

=== Using sysboot ===

<code>extlinux.conf</code> should have the following contents:

<pre>
timeout 10
default MAINLINE
menu title boot prev kernel

label MAINLINE
kernel /vmlinuz
fdt /rk3566-pinenote.dtb
initrd /initramfs
append earlycon console=tty0 console=ttyS2,1500000n8 fw_devlink=off PMOS_NO_OUTPUT_REDIRECT
</pre>

At the u-boot console, run the following command to boot your mainline kernel:

<pre>
sysboot ${devtype} ${devnum}:9 any ${scriptaddr} extlinux.conf
</pre>

=== Booting with individual commands ===

Booting with individual commands can be useful when you need to temporarily add some kernel command line arguments. Use these or similar commands at the U-Boot shell:

load mmc 0:b ${kernel_addr_r} boot/Image
load mmc 0:b ${fdt_addr_r} boot/rk3566-pinenote.dtb
setenv bootargs ignore_loglevel root=/dev/mmcblk0p11 rootwait init=/bin/bash
booti ${kernel_addr_r} - ${fdt_addr_r}

== Configuration ==

=== Firmware for WiFi & Bluetooth and Waveform data ===

==== Using Maximilian's Debian image ====
If the Android partition (super) and waveform partition (waveform) is left intact the image extracts the WiFi, BT driver and waveform from the partitions on first run.

For instance if you repartitions the userdata partition and installs the image there.

==== Getting it from the Android install manually ====
Copy WiFi/BT firmware from Android:
mkdir -p /cache/lib/firmware/brcm
cp /vendor/etc/firmware/fw_bcm43455c0_ag_cy.bin /cache/lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /vendor/etc/firmware/nvram_ap6255_cy.txt /cache/lib/firmware/brcm/brcmfmac43455-sdio.txt
cp /cache/lib/firmware/BCM4345C0.hcd /cache/lib/firmware/brcm/BCM4345C0.hcd

Copy waveform partition (via previously dumped file):
adb root
adb push waveform.img /cache/lib/firmware/waveform.bin

Or via dd within Linux:
dd if=/dev/mmcblk0p3 of=/lib/firmware/waveform.bin bs=1k count=2048

==== Getting the Wifi and Bluetooth driver blobs from "other" sources ====
===== WiFi =====
The WiFi firmware .bin blob can be obtained by installing the Debian package firmware-brcm80211 (in the non-free section)

The WiFi brcmfmac43455-sdio.txt file can according to Eugen be sourced from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm/brcmfmac43455-sdio.AW-CM256SM.txt needs a renaming when copying it to /lib/firmware/brcm/brcmfmac43455-sdio.txt)

''The content of the upstream .txt is different than the Android configuration, but is supposed to work.''

As you don't have WiFi yet you need to get the firmware-brcm80211*.deb and brcmfmac43455-sdio.txt file on the PineNote by other means, for instance using an USB stick

===== Bluetooth =====

Once you have WiFi working you can get BCM4345C0.hcd by installing the bluez-firmware
sudo apt install bluez-firmware

=== Configuring the E-ink refresh mode ===
https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches contains information on how/where to write in /sys to alter the refresh mode

https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension contains the gnome extension used in Maximilian image

=== Touchscreen and Pen In X.org ===

By default the pen config is flipped 180° (which makes it unusable) and the touchscreen doesn't work. Placing the following config in <code>/etc/X11/xorg.conf.d/50-touchscreen.conf</code> will fix both problems:

<pre>
Section "InputClass"
Identifier "evdev touchscreen"
MatchProduct "tt21000"
MatchIsTouchscreen "on"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "RotateTouch"
MatchProduct "w9013"
Option "TransformationMatrix" "-1 0 1 0 -1 1 0 0 1"
EndSection
</pre>

PineNote

2023-01-10T09:04:19Z

Mweigand: Mention the Debian rootfs/disc in State of the software

[[File:PineNote-1.jpg|400px|thumb|right|The PineNote]]

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.

== Introduction ==

=== State of the software ===

The PineNote is based on the in 2021 released Rockchip RK3566 SoC. The upstreaming status of the SoC functionality can be found on the [[Quartz64 Development#Upstreaming Status|Quartz64 development]] wiki page of the Quartz64 single-board computer using the same SoC.

The early adopter's batch of the PineNote is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive Linux experience. If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation. It may not even boot to a graphical environment.

An early version of a GNOME-based Debian image is available for [[PineNote_Development/Installing_Debian|testing]], but should not be expected to meet general-user readiness.

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== Specification ==
[[File:PineNote_Pen_function.jpg|300px|right]]
[[File:PineNote_Cover-1.jpg|300px|right]]

=== General Information ===
* Dimensions: 191.1x232.5x7.4mm
* Weight: 438g

=== Core ===
* CPU: RK3566 1.8GHz 64-bit quad-core A55
* GPU: MALI G52 2EE
* System memory: 4GB LPDDR4
* Flash: 128GB eMMC

=== E-ink Display ===
* Size: 10.3"
* Resolution: 1404x1872
* DPI: 227
* Grayscale: 16
* Front Light: 36 level cold and warm
* Capacitive multi-touch panel
* EMR pen digitizer

=== Network ===
* WiFi: 2.4/5GHz 802.11a/b/g/n/ac
* Bluetooth: 5.0

=== Audio ===
* Built in stereo speakers
* 4 x DMIC microphone

=== Sensor ===
* G-Sensor for portrait and landscape sensing

=== Power ===
* 4000mAH LiPo battery
* DC 5V @ 3A USB-C connector

=== Accessories ===
* Optional EMR pen with magnetic attachment (included in the first production batch)
* Optional Cover (included in the first production batch)

== Software releases ==
* Not yet available

== SoC and Memory Specifications ==
* Based on [https://www.rock-chips.com/a/en/products/RK35_Series/2021/0113/1274.html Rockchip RK3566]
[[File:RK3566_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a55 Quad-core ARM Cortex-A55@1.8GHz]
* AArch32 for full backwards compatibility with ARMv7
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* Includes VFP hardware to support single and double-precision operations
* ARMv8 Cryptography Extensions
* Integrated 32KB L1 instruction cache and 32KB L1 data cache per core
* 512KB unified system L3 cache
* [https://developer.arm.com/ip-products/security-ip/trustzone TrustZone] technology support
* [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]

=== GPU (Graphics Processing Unit) Capabilities ===
* [https://developer.arm.com/ip-products/graphics-and-multimedia/mali-gpus/mali-g52-gpu Mali-G52 2EE Bifrost GPU@800MHz]
* 4x Multi-Sampling Anti-Aliasing (MSAA) with minimal performance drop
* 128KB L2 Cache configurations
* Supports OpenGL ES 1.1, 2.0, and 3.2
* Supports Vulkan 1.0 and 1.1
* Supports OpenCL 2.0 Full Profile
* Supports 1600 Mpix/s fill rate when at 800MHz clock frequency
* Supports 38.4 GLOP/s when at 800MHz clock frequency

=== NPU (Neural Processing Unit) Capabilities ===
* Neural network acceleration engine with processing performance of up to 0.8 TOPS
* Supports integer 8 and integer 16 convolution operations
* Supports the following deep learning frameworks: TensorFlow, TF-lite, Pytorch, Caffe, ONNX, MXNet, Keras, Darknet

=== System Memory ===
* RAM Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== PineNote Information, Schematics, and Certifications ==
* PineNote Developer kit version
* The v1.2 is the PineNote production schematic.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R2%20-%20Schematic-20210824.pdf PineNote Mainboard Schematic ver 1.2 20210824 PDF file]
** [https://files.pine64.org/doc/PineNote/PINENOTE_USB-C-Board-V1.0-sch.pdf PineNote USB-C Daughter Board Schematic ver 1.0 PDF file]
** [https://files.pine64.org/doc/PineNote/PineNote_USB-C_Console_UART_breakout_board_schematic_v1.0_20210903.pdf PineNote USB-C Console UART Breakout Board Schematic ver 1.0 PDF file]
* The v1.1 is early release schematic just for reference only and used by developers who received the prototype.
** [https://files.pine64.org/doc/PineNote/PINENOTE_MAIN-V1R1%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
** [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]

* Certifications:
** [https://files.pine64.org/doc/cert/PineNote%20FCC15C%20Certificate%20DTS-TC561262.pdf PineNote FCC-15C Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20FCC15E%20Certificate%20NII-TC973072.pdf PineNote FCC-15E Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20CE%20RED%20Certicate%20ET-21090682EC.pdf PineNote CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineNote%20RoHS%20Certificate%20ET-210900082C.pdf PineNote ROHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3566 SoC information:
** [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]
* Rockchip RK817 PMU (Power Management Unit) Information:
** [https://www.rockchip.fr/RK817%20datasheet%20V1.01.pdf Rockchip RK817 ver 1.01 datasheet]
* LPDDR4 (200 Balls) SDRAM:
** ---
* eMMC information:
** [https://en.biwin.com.cn/product/detail/6 Biwin 128GB eMMC model: BWCTASC41P128G]
* E-ink Panel information:
** [https://files.pine64.org/doc/quartz64/Eink%20P-511-828-V1_ED103TC2%20Formal%20Spec%20V1.0_20190514.pdf E-Ink 10.3" 1872x1404 ED103TC2 Glass Panel Specification]
** [https://files.pine64.org/doc/datasheet/PineNote/TI%20PMU-TPS651851.pdf TPS65185x PMIC for E-Ink Enabled Electronic Paper Display Datasheet]
* Touch Screen information:
** [https://files.pine64.org/doc/datasheet/PineNote/CYTMA448_Summary_RevC_5-26-16.pdf Cypress CYTMA448 multi-Point Capacitive Touch Controller Datasheet]
** Wacom Pen Digitizer Unit Model: SUDE-10S15MI-01X for 10.3" Display Module
* WiFi/BT module info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AW-CM256SM_DS_DF_V1.9_STD.pdf Azurewave CM256SM 11AC WiFi + Bluetooth5.0 Datasheet]]
* G Sensor info:
** [http://www.silan.com.cn/en/product/details/47.html#app01 Silan SC7A20 3-Axis MEMS Accelerometer]
* Audio Amplifier information:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]

== Development Efforts ==

* [[PineNote Development]] for general information regarding how to flash the device and other development information.

=== Software ===

* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.

=== Hardware ===

This section includes discussions and their results regarding hardware changes to the PineNote.

The following topics have resolved:

* [[PineNote/Hardware_Changes/Closed_Case_UART]]
* '''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.
* '''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.
* '''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.
* '''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, and screen face down, 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.

==== Unresolved ====

The following concerns have been brought up as open, unanswered topics:

* 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). Note that Audio Accessory mode is detectable by reading the I2C registers of the WUSB3801Q. So connecting ASEL to a GPIO would be enough to get this working if it is not working already.
* 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.
* 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.
* Is there any way to indicate when the device is in rockusb mode, such as connecting a certain magic pin to the power LED?
* The modem/4G connector (J6010) has its I2C and UART pins unconnected. Could those be connected to the SoC?

==== USB-C Debug Accesory Mode (DAM)/UART Dongle====
The USB UART dongle delivered with the PineNote allows you to have access to a serial port without having to open up the device. The factory firmware runs at a baud rate of 1500000bps, 8 data bits 1 stop bit, no parity and no flow control. The USB-C male end should go into the PineNote and the female end can be connected with a standard USB-C cable to your computer.

=== Documentation ===
PineNote development documentation is a little lacking. Unless you are relatively plugged in with the chat, it's difficult to know what is going on. There is an effort to amend that that lives here: [[PineNote Documentation]].

== BSP Linux SDK ==

=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC ===
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_BSP%20Linux.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_BSP%20Linux.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67.00GB

== Android SDK ==

=== Android 11 eink SDK for PineNote and Quart64 model A SBC ===
* This is the Android SDK build for 10.3" eink panel on Quartz64 model A SBC.
* [http://files.pine64.org/SDK/Quartz64/QUARTZ64-model-A_eink.android11_SDK.tar.gz Direct Download from pine64.org]
** [https://tmp.mwfc.info/pinenote/QUARTZ64-model-A_eink.android11_SDK.tar.gz mirror by mwfc]
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
* View [[Android SDK for RK3566]] for more information how to compile an image for the PineNote using this SDK

== Torrent ==
There is a [https://cdn.discordapp.com/attachments/870707390998282292/907726420204208148/pinenote.torrent torrent] with the files (100GB)

== Hardware troubleshooting guide ==
At present, nothing is available.

[[Category:PineNote]] [[Category:Rockchip RK3566]]

PineNote Development

2023-01-10T08:51:54Z

Mweigand: Start working on a table with mainlinging information for kernel modules required by the PineNote (work in progress)

This article seeks to provide general development information for the [[PineNote]]. If you are new and down to try a new installation process, the easiest way to get linux is likely to [https://wiki.pine64.org/wiki/PineNote_Development/Installing_Debian install Debian] -- NOTE THAT THIS INSTALLATION PROCESS IS VERY NEW. While many people have been using the kernel that will be installed safely at this point, the instructions for installing Debian via rootfs are very new. Take backups!

The more stable recommended approach is described below:

Start with [https://github.com/DorianRudolph/pinenotes Dorian's guide] which will guide you through getting Arch installed. For instructions on building the latest kernel, see [[PineNote Development/Building Kernel]]. For helpful configurations, see [[PineNote Development/Apps]]. For ways to pitch in, see [[PineNote Development/TODOs]]. To boot Linux by default instead of Android, see [[PineNote Development/Booting Linux]]. [https://www.youtube.com/watch?v=ZCLyJfbzbrU Here is a video] of a user running Manjaro and some apps on their PineNote on 9/10/2022.

= Overview =

== Kernel modules / mainlining status ==

WORK IN PROGRESS !

The following table aims to provide a list of kernel modules required for running the PineNote.
It also aims at listing repositories of work in progress.
While some overlap with the Quartz64 module list ([[Quartz64_Development#Upstreaming_Status]])
is expected, only modules relevant to the PineNote hardware should be listed here.

{|class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
| Touchscreen
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| | <code>cyttsp5</code>
| kernel 6.2 merge window ?
|-
| Digitizer
| <code>?</code>
|-
| Pen BLE Buttons
| <code>ws8100-pen</code>
|-
| EBC Display controller
| <code>rockchip_ebc</code>
|-
| EBC PMic
|<code>tps65185</code>
|-
| LED backlight driver
| lm3630a
|-
| Accelerometer
| <code>st-accel-i2c</code>
|-
| Rastergraphics unit RGA2e
| <code>rga</code> (v4l2 mem2mem driver)
|-
| Mali GPU
| <code>panfrost</code>
|-
| Wifi/BT
| ???
|}

= More Information =
== High-level developer new to embedded linux? ==
Here are some resources I have found helpful in learning to develop on embedded linux devices:
* Great youtube series introducing you to the kernel and lower-level components of Linux: https://www.youtube.com/watch?v=WiZ05pnHZqM
* https://embetronicx.com/
* https://bootlin.com/training/
* https://www.nand2tetris.org

== Notes Written by Some Developers ==

* https://github.com/m-weigand/mw_pinenote_misc (Not super legible "notes", but very helpful repo with patches, videos, etc)
** specifically see this section for helpful install/configure scripts: https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches#compiling.
* https://github.com/0cc4m/pinenote-misc
** patch for enabling gpu: https://github.com/0cc4m/pinenote-misc/blob/main/mesa-archlinux-arm/mesa/rockchip_ebc.patch
** prebuilt pkg's: https://github.com/0cc4m/pinenote-misc/releases
* https://pwarren.id.au/pinenote/build_notes.txt
* https://github.com/DorianRudolph/pinenotes
* https://github.com/tpwrules/nixos-pinenote

== Alternative to patching of mesa ==
Mesa needs to be patched to add the driver entry point. The alternative to this, is the renaming of the ebc driver to an existing mesa driver entry point. A good existing name can be "repaper". To change the driver name, edit in the kernel tree the following files: 
- replace "rockchip-ebc" with "repaper" in the two places in the file: drivers/gpu/drm/rockchip/rockchip_ebc.c 
- preventive, replace "repaper" with "repaper-disabled" in the two places in the file: drivers/gpu/drm/tiny/repaper.c 

== Building the most recent kernel ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel here].

== Video of Factory Android OS ==

[https://www.youtube.com/watch?v=DWuTGgQHw98 PineNote Developer Edition w/Tech Demo Android OS (Video Only)]

Informal walkthrough of the factory Android installation on the PineNote Developer Edition, recorded by a community member (Apr 2022). This is useful to look back at the original OS after erasing it from your device, or to get some additional detail before your device arrives.

The video also includes a chapter at the end showing [https://www.youtube.com/watch?v=DWuTGgQHw98&t=802s how to enable Android Debug Bridge (`adb`) over USB]. Once enabled, keep the device powered and connect a USB cable directly to the PineNote (i.e. no UART breakout) to a computer running `adb`.

== Emulator for Developing/Testing Pinenote Apps ==
https://github.com/michaelshiel/picom-epaper

= Flashing Software =
Currently, the only ways to flash software are from the factory Android installation (UART shell, adb, or fastboot) or by using rkdeveloptool.

== Backup of the content of the internal MMC before you mess anything up ==
Especially the '''waveform''' partition contains data '''unique''' to your PineNote and is a prime candidate for backup.

But other partitions like uboot (need for any operation of the device) or the un-partitioned space at the beginning containing the GPT partition table (and presumably the VCOM setting for the e-ink display and maybe device mac addresses) contains data you may wish to backup.

Depending of your personal level of data hoarder you may want to backup more than this or even just everything (the large userdata partition is supposed to be able to be repopulated as empty space by Android)

In any case it is easier to restore/extract data from a backup than not having one if you need one.

=== Manually using rkdeveloptool ===
Dorian has some nice [https://github.com/DorianRudolph/pinenotes notes regarding the PineNote]

Don't forget to install a patched uboot for reading beyond 32MB and to respect the 2GB limit/bug of the current rkdeveloptool as per his notes

=== Automated backup using a script and rkdeveloptool ===
[https://github.com/talpadk/pinenote-backup pinenote-backup] is a python script for detecting the partitions and automating the backup of partitions or the whole disk

I also requires a patched u-boot but automatically handles the 2GB limit by splitting up larger reads into smaller ones

=== Using the factory Android installation ===
For any one knowing how and with which caveats: Write ME

=== Using a user installed Linux ===
A Linux installed to the cache partition should be able to easily backup everything over WiFi or to a USB stick/disk using dd

However the user would need to backup the cache partition themself (if they want that).

And more importantly they would only be getting the backup ''after'' they started playing with the content of the MMC.

== Side-by-side setup ==

It is possible to set up a partition for mainline development without disturbing the factory Android installation. This allows updating a mainline kernel, DTB, and initramfs over Wi-Fi until WiFi or USB OTG is working in mainline Linux.

=== Without Repartitioning ===

The recommended partition for this is <tt>mmcblk0p11</tt> aka <tt>/cache</tt>. It is large and already formatted as <tt>ext4</tt>, so it is readable from U-Boot. Here are some general steps:

# From the UART or adb shell, set up your chroot in <tt>/cache</tt>. I used the Alpine Linux rootfs tarball.
# Copy in your kernel and DTB, using for example <tt>scp</tt> or <tt>wget</tt> inside the chroot.
# Finally, create and boot an <code>extlinux.conf</code> as described below.

=== With Repartitioning ===

It is possible to shrink the <tt>userdata</tt> partition, and create a new partition at the end for use with mainline Linux. This provides much more space than <tt>cache</tt>. However, because <tt>userdata</tt> is formatted with <tt>f2fs</tt>, and that filesystem cannot be shrunk, resizing the partition requires wiping <tt>userdata</tt>.

# Back up any necessary files from userdata
# Boot to a mainline kernel from <tt>mmcblk0p11</tt>, either using that partition as rootfs (see above), or using an initramfs with repartitioning tools
# Modify the partition table with your favorite tool, e.g. <tt>fdisk</tt>, <tt>gdisk</tt>, or <tt>parted</tt>
# Reboot into <tt>fastboot</tt> and wipe <tt>userdata</tt>.
# Reboot into Android, where you can now chroot in and install your favorite distribution to the new partition.

== Using rkdeveloptool ==

rkdeveloptool is a command line utility built on libusb.

=== Downloading and Building rkdeveloptool ===

PINE64 develops [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool its own updated fork of rkdeveloptool on GitLab].

You will need to have libusb 1.0, its development headers and scdoc installed.

<pre>
git clone https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool.git
cd rkdeveloptool
mkdir build
cd build
cmake ..
</pre>

This sets up all the build files. You can then compile with <code>make</code> inside the build directory.

After you're done, you'll likely also need to install the udev rules, or else your user won't have permission to access the USB devices:

<pre>
sudo cp 99-rk-rockusb.rules /etc/udev/rules.d/
sudo udevadm control --reload
</pre>

Copying the udev rules is also performed automatically when you <code>make install</code>.

=== Building Downstream U-Boot ===

While in maskrom mode, we need to have a u-boot to download onto the device for any of the other commands to work. To build you'll also need to install device-tree-compiler.

You also need to install Python and pyelftools.

 Note that rkbin is a >5GB download! This will take some time to clone and process the deltas.

<pre>
git clone -b quartz64 https://gitlab.com/pgwipeout/u-boot-rockchip.git
git clone -b rkbin https://github.com/JeffyCN/rockchip_mirrors.git rkbin
cd u-boot-rockchip
# If using Arch Linux, export CROSS_COMPILE=aarch64-linux-gnu-
export CROSS_COMPILE=aarch64-none-linux-gnu-
make rk3566-quartz64_defconfig
./make.sh
</pre>

<blockquote>
In the version I cloned (current as of 2022-01-02), I had to make a change to one line to get a clean compilation:

<pre>
diff --git a/lib/avb/libavb/avb_slot_verify.c b/lib/avb/libavb/avb_slot_verify.c
index 123701fc3b..64a1ce6450 100644
--- a/lib/avb/libavb/avb_slot_verify.c
+++ b/lib/avb/libavb/avb_slot_verify.c
@@ -296,7 +296,7 @@ static AvbSlotVerifyResult load_and_verify_hash_partition(
bool image_preloaded = false;
uint8_t* digest;
size_t digest_len;
- const char* found;
+ const char* found = NULL;
uint64_t image_size;
size_t expected_digest_len = 0;
uint8_t expected_digest_buf[AVB_SHA512_DIGEST_SIZE];
</pre>

For systems where the global python executable points to python2, compilation fails with an error related to pyelftools not being installed (even if it is). To fix this:
<pre>
diff --git a/make.sh b/make.sh
index 2bba05b4e4..cfe5b0afd5 100755
--- a/make.sh
+++ b/make.sh
@@ -758,7 +758,7 @@ function pack_fit_image()
fi

if [ "${ARM64_TRUSTZONE}" == "y" ]; then
- if ! python -c "import elftools" ; then
+ if ! python3 -c "import elftools" ; then
echo "ERROR: No python 'pyelftools', please: pip install pyelftools"
exit 1
fi
</pre>
</blockquote>

=== Entering Maskrom/Rockusb Mode ===

There are three ways to get into Maskrom/Rockusb mode:

==== The easy way ====

# Flip the device around so that the display faces down
# Lay the pen on the right side, with its tip pointing towards the speaker grill, and its magnet pointing towards the upper right corner of the label on the back (or place the magnetic cap from the pen on the spot marked on the back).
# Turn the device on and wait for it to show up in <code>lsusb</code>. It should now be in Loader mode, according to <code>rkdeveloptool list-devices</code> (note that "Loader" here indicates U-Boot's Rockusb; separately, booting with an erased eMMC displays "Maskrom" [not "Loader"] from the RK3566).
# Unplug the device and plug it back in. It should now be in Rockusb mode.

This can be a bit fiddly to get right, and may need a few tries.

==== The u-boot way ====
# Interrupt the u-boot startup using ctrl-c (while attached using an UART dongle)
# While in u-boot use the command "rockusb 0 mmc 0" to start rockusb mode.

One benefit from this is, that if you have an UART dongle that allows to simultaneous having an UART and USB connection, there is no need to plug and unplug cables and flipping the PineNote around and placing magnets.

This is especially helpful when changing back and forth between u-boot and rockusb, for instance when trying to develop u-boot.

==== Shorting test points ====

If the bootloader is broken/corrupted, you cannot get to Maskrom without opening up the device (it can be opened using spudger and a bit of patience).

Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb):

[[File:PineNote_Maskrom_TP.png|500px]]

Then plug the device to the computer and if you see the device with VID=2207/PID=350a then it should be in Maskrom mode, you can verify by typing <code>rkdeveloptool list-devices</code>.

<nowiki>Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device found, idVendor=2207, idProduct=350a, bcdDevice= 1.00
Jan 07 15:04:13 melttower kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ rkdeveloptool list-devices
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=10e Maskrom</nowiki>

If nothing shows up, you can try to hold down the power button for 5 seconds and then try again.

=== Running rkdeveloptool ===

First, you'll want to make sure the device you've connected is in maskrom mode:

<pre>
./rkdeveloptool list
</pre>

It should output something like <code>DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=202 Maskrom</code>. If it doesn't, see [[PineNote Development#Entering Maskrom Mode]].

You can now download u-boot onto it:
<pre>
./rkdeveloptool boot ../u-boot-rockchip/rk356x_spl_loader_v1.08.111.bin
</pre>

This should output <code>Downloading bootloader succeeded.</code>.

We can now verify that this worked using e.g. the "read flash info" command:

<pre>
./rkdeveloptool read-flash-info
</pre>

'''TODO:''' finish this section

=== Creating a mainline boot image ===

You can create a filesystem image that replaces the Android boot or recovery partition by doing roughly the following:

# Erase boot and dtbo with rkdeveloptool or fastboot (back them up first!!!)
# Create an ext2 partition image and mount it (fallocate, mkfs.ext2)
# Build your mainline kernel
# Copy the kernel, dtb and an initramfs to the root of the mounted image (use any old postmarketOS initramfs)
# Create a file in the root of the mounted image called <code>extlinux.conf</code> as described below
# Unmount the image and then use rkdeveloptool to flash it to the "recovery" partition on the pinenote (it's about the right size until we get around to replacing the partition layout).

== Using fastboot ==

Follow the steps for "Creating a mainline boot.img", but instead of flashing it with rkdeveloptool, use fastboot. You can enter fastboot in either of two ways:

# Use "reboot bootloader" from adb or a UART console.
# Get a U-Boot prompt and run <code>fastboot usb 0</code>.

= Mainline development =

== Status ==

Some work happening here: https://gitlab.com/calebccff/linux, the idea is to import the parts of the eink/ebc drivers which are open source and use the downstream u-boot framebuffer driver as a reference to create a basic framebuffer driver.

Currently mainline struggles to boot due to weird issues while probing fixed regulators (?). It also fails to detect eMMC.

Further work is being done here: https://github.com/smaeul/linux/commits/rk356x-ebc-dev. This has a complete device tree, with working eMMC. Pen input also works out of the box. Wi-Fi and BT work with firmware copied from the factory Android image.

== How to boot mainline ==

UART is currently REQUIRED for this to work! We depend on u-boot falling back to console. Once we have a prebuilt u-boot which will use extlinux by default, UART won't be needed anymore.

You can compile a u-boot that uses extlinux by default by following the instructions [https://github.com/JoshuaMulliken/pinenote_uboot/blob/aa9ecbd3d3e716f163f5a900824630f24e9f04ba/README.md#changing-default-boot-order here].

=== Getting to a U-Boot prompt ===

You can get to a U-Boot prompt by:

# Holding Ctrl-C while the display panel initializes.
# Wiping the "boot" partition.

=== Using sysboot ===

<code>extlinux.conf</code> should have the following contents:

<pre>
timeout 10
default MAINLINE
menu title boot prev kernel

label MAINLINE
kernel /vmlinuz
fdt /rk3566-pinenote.dtb
initrd /initramfs
append earlycon console=tty0 console=ttyS2,1500000n8 fw_devlink=off PMOS_NO_OUTPUT_REDIRECT
</pre>

At the u-boot console, run the following command to boot your mainline kernel:

<pre>
sysboot ${devtype} ${devnum}:9 any ${scriptaddr} extlinux.conf
</pre>

=== Booting with individual commands ===

Booting with individual commands can be useful when you need to temporarily add some kernel command line arguments. Use these or similar commands at the U-Boot shell:

load mmc 0:b ${kernel_addr_r} boot/Image
load mmc 0:b ${fdt_addr_r} boot/rk3566-pinenote.dtb
setenv bootargs ignore_loglevel root=/dev/mmcblk0p11 rootwait init=/bin/bash
booti ${kernel_addr_r} - ${fdt_addr_r}

== Configuration ==

=== Firmware for WiFi & Bluetooth and Waveform data ===

==== Using Maximilian's Debian image ====
If the Android partition (super) and waveform partition (waveform) is left intact the image extracts the WiFi, BT driver and waveform from the partitions on first run.

For instance if you repartitions the userdata partition and installs the image there.

==== Getting it from the Android install manually ====
Copy WiFi/BT firmware from Android:
mkdir -p /cache/lib/firmware/brcm
cp /vendor/etc/firmware/fw_bcm43455c0_ag_cy.bin /cache/lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /vendor/etc/firmware/nvram_ap6255_cy.txt /cache/lib/firmware/brcm/brcmfmac43455-sdio.txt
cp /cache/lib/firmware/BCM4345C0.hcd /cache/lib/firmware/brcm/BCM4345C0.hcd

Copy waveform partition (via previously dumped file):
adb root
adb push waveform.img /cache/lib/firmware/waveform.bin

Or via dd within Linux:
dd if=/dev/mmcblk0p3 of=/lib/firmware/waveform.bin bs=1k count=2048

==== Getting the Wifi and Bluetooth driver blobs from "other" sources ====
===== WiFi =====
The WiFi firmware .bin blob can be obtained by installing the Debian package firmware-brcm80211 (in the non-free section)

The WiFi brcmfmac43455-sdio.txt file can according to Eugen be sourced from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm/brcmfmac43455-sdio.AW-CM256SM.txt needs a renaming when copying it to /lib/firmware/brcm/brcmfmac43455-sdio.txt)

''The content of the upstream .txt is different than the Android configuration, but is supposed to work.''

As you don't have WiFi yet you need to get the firmware-brcm80211*.deb and brcmfmac43455-sdio.txt file on the PineNote by other means, for instance using an USB stick

===== Bluetooth =====

Once you have WiFi working you can get BCM4345C0.hcd by installing the bluez-firmware
sudo apt install bluez-firmware

=== Configuring the E-ink refresh mode ===
https://github.com/m-weigand/mw_pinenote_misc/tree/main/rockchip_ebc/patches contains information on how/where to write in /sys to alter the refresh mode

https://github.com/m-weigand/mw_pinenote_misc/tree/main/gnome_extension contains the gnome extension used in Maximilian image

=== Touchscreen and Pen In X.org ===

By default the pen config is flipped 180° (which makes it unusable) and the touchscreen doesn't work. Placing the following config in <code>/etc/X11/xorg.conf.d/50-touchscreen.conf</code> will fix both problems:

<pre>
Section "InputClass"
Identifier "evdev touchscreen"
MatchProduct "tt21000"
MatchIsTouchscreen "on"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "RotateTouch"
MatchProduct "w9013"
Option "TransformationMatrix" "-1 0 1 0 -1 1 0 0 1"
EndSection
</pre>

PineNote Development/TODOs

2022-10-31T07:07:41Z

Mweigand: add link back to main pinenote page and add empty "kernel todo" section

{{Template:Under construction}}

[[PineNote|Back to PineNote main page]]

TODOs to get the pinenote to a user ready state. If you know the answer to one of these or want something to do, please make a page with this info and link it here :)

= Kernel/driver TODOs=

= Userspace TODOs=
== Themes ==
A lot of getting the PineNote to work nicely will be theming things appropriately. Please list themes for various components here:
=== GNOME ===
Untested as far as I know: https://github.com/fujimo-t/gnome-shell-theme-e-ink
=== GTK ===
Todo

== GNOME Configurations ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps#Gnome here].
== Sway Configurations ==
See [https://wiki.pine64.org/wiki/PineNote_Development/Apps#Sway here].

== Open questions that would be helpful during development ==
# How do we pin packages so Mesa isn't updated when we update using our package manger?

= Documentation TODOs =
{{info|These are things we know how to do, but they just haven't been documented in the wiki yet. If you know how to do one of these things, please make a page for it. If you aren't sure where to put it or just don't feel like doing it, please just message @aarondabomb on matrix and I'll be happy to document it.}}

=== Pin Mesa Packages so they don't update when we upgrade other packages ===
Should be super simple, I just don't know how. If you know, it would be helpful for you to add that information near step 5 [https://wiki.pine64.org/wiki/PineNote_Development/Building_Kernel#Steps_to_build here].
=== Control the backlight? ===
=== Building alacritty correctly ===
=== Force a screen refresh? ===
Maximilian mentioned how to do this, but I don't know enough to know what it means XD see conversation here: https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$tfumBpnP2UPouNpaeFrggR40ZkrD_pHAtJdQmQvzL-o?via=matrix.org&via=kde.org&via=tchncs.de