Difference between revisions of "PineNote"

Jump to navigation Jump to search
(Rewrite strikethrough section as introduction to paragraph,)
(18 intermediate revisions by 9 users not shown)
Line 1: Line 1:
[[File:PineNote-1.jpg|frame]]
[[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.
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.


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


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


=== Sensor ===
=== Sensor ===
Line 46: Line 45:
* Optional Cover (included in the first production batch)
* Optional Cover (included in the first production batch)


 
== Software releases ==
== Software and OS Image Downloads ==
 
* Not yet available
* Not yet available


== SoC and Memory Specifications ==
== SoC and Memory Specifications ==
Line 87: Line 83:


== PineNote Information, Schematics, and Certifications ==
== PineNote Information, Schematics, and Certifications ==
* PineNote Developer kit version
* The early release schematic just for reference only and used by developers who received the prototype.
** [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 early release schematic just for reference only and used by developers who received the prototype.  
* The 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%20-%20Schematic-20210726.pdf PineNote early released Schematic ver 1.1 20210726 PDF file]
Line 92: Line 93:


* Certifications:
* Certifications:
** Not yet available
** [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 ==
== Datasheets for Components and Peripherals ==
Line 116: Line 120:
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]
** [https://files.pine64.org/doc/datasheet/PineNote/Awinic%20AW87318%20Class-K%20Audio%20Amp%20Datasheet.pdf Awinic AW87318 Class-K Audio Amp Datasheet]


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


=== Software ===
=== Software ===


* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC
* [[Quartz64 Development]] for the mainlining status of various functions on the Rockchip RK3566 SoC.
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver
* [[RK3566 EBC Reverse-Engineering]] for the EBC (eInk Panel) driver.


=== Hardware ===
=== Hardware ===
Line 128: Line 133:
This section includes discussions and their results regarding hardware changes to the PineNote.
This section includes discussions and their results regarding hardware changes to the PineNote.


==== Closed-Case UART ====
The following topics have resolved:
 
Developers usually don't like taking their devices apart to debug bootloaders. Therefore, it is important to provide resources to debug the PineNote's boot process such as a hardware UART. Recent PINE64 devices have included a hardware UART connected to their 3.5mm TRRS jacks through a hardware switch. However, the PineNote doesn't have an audio jack. It also doesn't have a convenient place to put a hardware switch which is accessible without taking the device apart. The case only has the affordance for a single USB-C port.


We decided to ask the PineNote product team to explore USB-C Debug Accessory Mode, where the product changes the USB-C port's personality when both CC1 and CC2 are pulled high. In normal usage, either CC1 or CC2 will be floating since these are the connector rotation pins. When both are detected, there is a very good chance that a debug harness is connected.
* [[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. However, revisions of the PineNote motherboard after 1.1 will feature an internal ribbon cable connector where a microSD card slot may be attached. Attaching such a device will require taking the PineNote apart.
* '''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.


This decision requires the PineNote motherboard to be able to detect an AND condition between CC1 and CC2 and connect one of the SOC's UARTs to pins on the USB-C connector. In all other cases, the UART should be disconnected. It also requires the PINE64 Store ship a simple one-sided (no magical flipping here, sorry) connector board which breaks out USB 2.0 and UART.
==== Unresolved ====


There are concerns that cheap USB-C cables have both CC1 and CC2 shorted together to save a wire. This may cause the PineNote to output 3.3v UART to a device that isn't expecting it, assuming the two are plugged together with a nonstandard cable.
The following concerns have been brought up as open, unanswered topics:


There were concerns that checking CC1 and CC2 being pulled high was not strictly to USB-C standard, as detecting them being pulled low is mentioned in the standard. However,h etecting a pull-up condition is all that is required. According to the USB-C spec, 'B.2.4.1.5.1 ("UnattachedDeb.SRC Requirements"), a Debug and Test System (DTS) that is a power source must pull CC1/CC2 up, while the Target System (TS) in Unattached.SNK is supposed to pull them low.' In English, this means that we'd only need to detect a pull-up condition on CC1 and CC2, meaning a logical AND between them is a sane solution.
* 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.
IRC logs of this discussion can be found at [[PineNote/Debug_Accessory_Mode_Discussion]].
* 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?


It should be possible to make the UART connection and breakout cable magically flippable by connecting the UART multiple times to the USB-C port.
==== 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.


== BSP Linux SDK ==
== BSP Linux SDK ==
Line 147: Line 158:
=== BSP Linux SDK ver 4.19 for PineNote and Quart64 model A SBC  ===
=== 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]
* [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
** MD5 (TAR-GZip file): 24554419aec29700add97167a3a4c9ed
** File Size: 32.67.00GB
** File Size: 32.67.00GB
Line 155: Line 167:
* This is the Android SDK build for 10.3" eink panel on Quartz64 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]
* [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
** MD5 (TAR-GZip file): 293a550584298de4fb95ceae18103672
** File Size: 72.88GB
** File Size: 72.88GB
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
** Just the boot blobs (<1MB): [[File:Rk35-blobs.tar.gz]]
== 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]]
[[Category:PineNote]] [[Category:Rockchip RK3566]]

Navigation menu