PINE64 - User contributions [en]

QuartzPro64 Development

2025-01-01T01:09:31Z

Dsimic: /* Documentation */ Added link to Rockchip RK3588 EVB User Guide

[[File:Quartzpro64_whole_board_top_resized.jpeg|250px|thumb|right|The QuartzPro64 development board, front side]]
[[File:BoardBackSide.jpg|250px|thumb|right|Back side of the board]]

A '''QuartzPro64 Development''' Wiki page before a '''QuartzPro64''' Wiki page? It's more likely than you think!

This page will be used for both documenting the current development efforts and the board in general, as we don't know yet how a generally available QuartzPro64 will look like so documenting the dev board is probably best left to the development page.

== Obtaining a Development Board ==

Register for a preorder: [https://preorder.pine64.org/#/quartzpro64 https://preorder.pine64.org/#/quartzpro64]

== Upstreaming Status ==

* Upstream Linux kernel DT: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3588-quartzpro64.dts
* Upstream U-Boot DT: https://github.com/u-boot/u-boot/blob/master/arch/arm/dts/rk3588-quartzpro64-u-boot.dtsi

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
! scope="row" | Video Output
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>VOP2</code>
| Collabora said they'll work on this. The video output IP on the RK3588 should mostly be the same as the one on the RK356x, but the chip specific stuff will need to be integrated into the vop2 driver.
|-
! scope="row" | Video Input
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rk_hdmirx</code>
| Huge 3600 line driver, but generally seems to be in good condition
|-
! scope="row" | 3D Acceleration
| style="background:#F99; text-align:center;"|Needs writing
| style="background:#F99; text-align:center;"|Needs writing
| <code>panfrost</code>
| Collabora said they'll work on this. New architecture, reportedly needs many changes to the kernel component of Panfrost.
|-
! scope="row" rowspan="4" | Video Decode
| style="background:#F99; text-align:center;"|Needs writing
| style="background:LightYellow; text-align:center;" rowspan="4"|GStreamer only, no ffmpeg[https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=2898]
| <code>hantro</code> using <code>v4l2-requests</code>
| VDPU121 handling 1080p60 H.263/MPEG-4, MPEG-1 and MPEG-2
|-
| style="background:#F99; text-align:center;"|Needs writing
| <code>rkvdec2</code> using <code>v4l2-requests</code>
| Nobody is known to be working on this for now. VDPU346 handling 8K60 H.265, H.264, VP9 and AVS
|-
| style="background:#F99; text-align:center;"|Needs writing
| <code>rkdjpeg</code> using <code>v4l2-requests</code>
| [[User:CounterPillow]] is doing a little work on this. VDPU720 handling JPEG
|-
| style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=721724]
| <code>hantro</code> using <code>v4l2-requests</code>
| Collabora is working on this. VDPU981 handling 4K60 AV1
|-
! scope="row" rowspan="3" | Video Encode
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center; background:LightYellow;"|GStreamer only
| JPEG on VEPU121
| Driver already exists, only minor changes needed.
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.264 on VEPU580
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.265 on VEPU580
|
|-
! scope="row" rowspan="2" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-i2s-tdm</code>
| As of 6.2[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c619bd4268ff9895760dab303b4eb15ed3d0f7e9]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>es8388</code> CODEC
|
|-
! scope="row" | CRU
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>clk-rk3588</code>
| As of 6.2[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f1c506d152ff235ad621d3c25d061cb16da67214]
|-
! scope="row" | MMC
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>sdhci-of-dwcmshc</code>
| As of 5.19[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbbd8872825310b14bc6e04250d2cb5edcd55edb]
|-
! scope="row" | pinctrl
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>pinctrl-rockchip</code>
| As of 5.19[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fdc33eba11c5919199f3d13dc53571cc7bf19d7d]
|-
! scope="row" | GPIO
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-gpio</code>
| As of 6.1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc165ba48aaf7d792e99d0c7e4b12e9625bc73e3]
|-
! scope="row" | I2C
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk3x-i2c</code>
| Should be the same as RK3399, just needs devicetree work
|-
! scope="row" | SPI
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-spi</code>
| Should be the same as previous SoCs, just needs devicetree work
|-
! scope="row" | PMU
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=687286]
| <code>rk806</code>
| Talks over SPI
|-
! scope="row" | Regulators
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rk860</code>
| Talks over I2C
|-
! scope="row" | GMAC
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>dwmac-rk</code>
| As of 6.1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f2b60a0ec2826e5a2b2a1ddf68994a868dccbc1]
|-
! scope="row" | Power Domains
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-pm-domain</code>
| As of 6.1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6541b424ce1dda616d3946e839f015c984df7a99]
|-
! scope="row" | CAN
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip_canfd</code>
| Not broken out on the QuartzPro64, so we probably won't be the ones porting it
|-
! scope="row" | SPDIF TX
| colspan="2" style="background:#F99; text-align:center;"|May need porting
| <code>rockchip-spdif</code>
| Genuinely just needs the compatible string added, I think, otherwise we're all good. Not broken out on QuartzPro64 dev board
|-
! scope="row" | SPDIF RX
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip-spdifrx</code>
| Not broken out on QuartzPro64 dev board
|-
! scope="row" | PCIe
| colspan="2" style="background:#F99; text-align:center;"|May need porting
| <code>rockchip-dw-pcie</code>
| Downstream driver and upstream are quite different, look into how much work actually needs doing. Seems to be the same controller as rk3568 so maybe none?
|-
! scope="row" | NPU
| style="background:#F99; text-align:center;"|Needs porting/writing
| style="text-align:center;"|?
| <code>rockchip-rknpu</code>
|-
! scope="row" | USB 2.0
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=749871]
| <code>phy-rockchip-inno-usb2</code>
| There's probably more to USB 2 than just the PHY but this is what I found for now
|-
! scope="row" | USB 3.0
| colspan="2" style="background:#F99; text-align:center;"|?
| <code>?</code>
|
|-
! scope="row" | SATA
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>ahci-dwc</code>
| Just needs the compatible added to the bindings, done in [https://patchwork.kernel.org/project/linux-rockchip/list/?series=749876]
|-
! scope="row" | Thermal
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=687619]
| <code>rockchip-thermal</code>
|
|-
! scope="row" | Wifi & Bluetooth
| colspan="2" style="background:#F99; text-align:center;"|?
| <code>?</code>
|
|-
! scope="row" | HWRNG
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip-rng</code>
| The code & DT work is easy to port & working
|
|-
! scope="row" | RTC
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>hym8563</code>
| Should only need DT work (see [https://patchwork.kernel.org/project/linux-rockchip/list/?series=736799 here] for an example)
|-
! scope="row" | OTP
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=744118]
| <code>rockchip-otp</code>
|
|-
! scope="row" | SARADC
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=748188]
| <code>rockchip_saradc</code>
|
|}

== Hardware ==

[[File:Quartzpro64_soc_and_ram_resized.jpeg|200px|thumb|right|The SoC and RAM packages]]

=== General ===

* RK3588 SoC (8 cores: 4x A76 at 2.4 GHz + 4x A55 at 1.8 GHz)
* Mali G610MC4 GPU (4x Valhalla cores)
* 16 GB of LPDDR4X (SK hynix)
* 64 GB eMMC (Foresee, soldered)
* 1x USB-C (with video-alt mode)
* 1x USB-C (FTDI debug UART, FT232RL)
* 1x USB 3.0
* 2x USB 2.0
* 1x HDMI in
* 2x HDMI out
* 1x PCIe 3.0 slot (open-ended)
* 1x SD / TF card slot
* 2x SATA ports
* 2x Gigabit Ethernet (1x from SoC, 1x on PCIe, RTL8211F, RTL8111HS)
* 1x WiFi & Bluetooth module (AMPAK Tech AP6275PR3)
* 2x SMA Antenna
* 2x MIPI DPHY
* 1x MIPI D/C PHY
* 1x MIPI CSI
* 1x PWM Fan header (four pins)
* 1x RTC battery socket (CR1220, 3 V, see [[#Documentation|QuartzPro64 board schematics PDF]], page 21)
* 1x MIC (soldered)
* 1x audio output 3.5 mm jack
* DC 12 V power input

=== Cooler ===

The board comes with two cooler mounts, a 4-hole mount that appears to be spaced 55x55mm apart, and the ~60mm diagonal "northbridge heatsink" mount the ROCKPro64 and Quartz64 Model A uses.

RK3588 is slightly (<1mm?) taller than the DRAM chips, use a thick enough thermal pad instead of thermal compound.

=== UART ===

Plug in the USB-C port labelled "<tt>DEBUG PORT</tt>" on the QP64 board to another computer with a USB-A-to-C cable.

It will show up as a FT232 USB Serial adapter in <code>lsusb</code>:
<pre>
$ lsusb
[...]
Bus 005 Device 027: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
[...]
</pre>

Baud rate is 1.5 mbauds or 1500000.

Ensure you have the driver module loaded:
<pre>
# modprobe ftdi_sio
# lsmod | grep ftdi_sio
ftdi_sio 61440 0
usbserial 53248 1 ftdi_sio
usbcore 290816 7 ftdi_sio,usbserial,xhci_hcd,usbhid,usbkbd,usbmouse,xhci_pci
</pre>

If the above is not working, check the required driver is supported by your kernel, using one of the following commands:
<pre>
$ zgrep FTDI_SIO /proc/config.gz
CONFIG_USB_SERIAL_FTDI_SIO=m
$ grep FTDI_SIO "/boot/config-$(uname -r)"
CONFIG_USB_SERIAL_FTDI_SIO=m
</pre>

Using the <code>dmesg</code> command, you should see something like the following:
<pre>
[24784.535804] usb 5-3: new full-speed USB device number 3 using xhci_hcd
[24784.710714] usb 5-3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[24784.710723] usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[24784.710725] usb 5-3: Product: FT232R USB UART
[24784.710727] usb 5-3: Manufacturer: FTDI
[24784.710728] usb 5-3: SerialNumber: A10LLO86
[24784.723858] usbcore: registered new interface driver usbserial_generic
[24784.723865] usbserial: USB Serial support registered for generic
[24784.725286] usbcore: registered new interface driver ftdi_sio
[24784.725295] usbserial: USB Serial support registered for FTDI USB Serial Device
[24784.725348] ftdi_sio 5-3:1.0: FTDI USB Serial Device converter detected
[24784.725368] usb 5-3: Detected FT232RL
[24784.731685] usb 5-3: FTDI USB Serial Device converter now attached to ttyUSB0
</pre>

Then you can get console output from the QP64 with, for example:

<pre>
screen /dev/ttyUSB0 1500000
</pre>

=== Mounting Holes ===

Mounting holes are 3 mm in diameter, so standard standoffs can be used, preferably the 2.5 mm variant. See also the PCB layout PDF files, linked in the [https://wiki.pine64.org/wiki/QuartzPro64_Development#Documentation Documentation] section.

The height from the bottom of the PCB to the top of the USB ports as the tallest components is 18 mm, which can be used as a data point for selecting the suitable standoff length to place some acrylic top cover over the board. However, that doesn't account for the heatsink that needs to be mounted on the RK3588 SoC, for which a suitable rectangular hole can be cut in the top cover.

=== Storage ===

[[File:Quartzpro64_emmc_resized.jpeg|200px|thumb|right|The eMMC on the dev board]]

* Soldered 64 GB FORESEE eMMC chip, which comes pre-flashed with some Android build
* One microSD card slot
* Two SATA 3.0 ports (standard Molex power connector is not populated)

=== Power ===

[[File:Power_and_switch.jpg|100px|thumb|right|Power switch & barrel connector]]

You can provide power to the board via the 12V barrel connector, it's 5.5mm OD/2.1mm ID barrel 'coaxial' type "M" centre-positive, the ROCKPro64 5A power supply from the PINE64 store will work. (TODO: add alternative ways).

There is a hardware flip switch to power up / down the board.

=== PMU ===

[[File:Quartzpro64_pmu.jpeg|100px|thumb|right|The PMU]]

2x RK806-2, not RK808 compatible. It's a dual PMU configuration where one PMU is a subordinate of the other.

Verify this once we have access to SDK sources.

=== Ethernet ===

The RGMII ethernet port (near the SDCARD socket) is working if you use neg2led's linux-quartz64 repo.

The other port (near the sound jack) is hooked to the SoC via PCIe and is currently reported working (on the matrix channel) with latest neggles kernel.

== Boot ==

The board can boot from the following interfaces:
* SPI
* eMMC
* SD/MMC

TODO: in which priority / order are those boot options tried ?

== Recovery ==

In the case you erase the eMMC and are unable to boot the board, you can use rkdeveloptool to recover the board. While you can use the [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool Pine64 Fork], it is recommended to use [https://gitlab.com/cypheon/rkdeveloptool/-/tree/main?ref_type=heads cypheon's Fork] until some Pending PRs are merged in to [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool/-/merge_requests?scope=all&state=opened&author_username=cypheon resolve issues] with larger files. This is important when working with the larger 64 GB eMMC on the QuartzPro64.

With rkdeveloptool installed, you will also need the rk3588_spl_loader from rockchip to init the memory/flash when in maskrom mode. This can be downloaded from the [https://github.com/rockchip-linux/rkbin/blob/master/bin/rk35/rk3588_spl_v1.12.bin rockchip-linux/rkbin repo].

Build the rk3588_spl_loader:
'''git clone https://github.com/rockchip-linux/rkbin.git'''
Cloning into 'rkbin'...
[...]
Resolving deltas: 100% (11368/11368), done.
'''cd rkbin'''
'''./tools/boot_merger RKBOOT/RK3588MINIALL.ini'''
********boot_merger ver 1.34********
Info:Pack loader ok.
'''ls -lh rk3588_spl_loader_v1.16.113.bin'''
-rw-r--r-- 1 user group 477K Aug 18 17:23 rk3588_spl_loader_v1.16.113.bin

Entering maskrom can be done in a variety of ways:

* Hold the maskrom button (little white button labelled "MASKROM" next to SATA socket) during powerup, OR
* Enter rockusb mode, and execute "rkdeveloptool reboot-maskrom".
* Bork your eMMC and SD devices (how? erase?), in which case bootup will fallback to maskrom.

=== Dumping the eMMC ===

Boot the device into maskrom mode, and then verify rkdeveloptool can see the board.
'''# rkdeveloptool list'''
DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=503 Maskrom

Once the board shows up, load the rk3588_spl_loader you downloaded or built earlier, and verify that the eMMC can be seen.
'''# rkdeveloptool boot ./rk3588_spl_loader_v1.08.111.bin'''
Downloading bootloader succeeded.
'''# rkdeveloptool read-flash-info'''
Flash Info:
Manufacturer: SAMSUNG, value=00
Flash Size: 59000 MB
Flash Size: 120832000 Sectors
Block Size: 512 KB
Page Size: 2 KB
ECC Bits: 0
Access Time: 40
Flash CS: Flash<0>

You can now dump the eMMC using the read command. Note that first you have to calculate the eMMC size, which can be done using the output from the previous flash info command. You need to take the sector count, and times it by the sector size, to get the total number of bytes. So in the above example, 120832000*512 so the total flash size is 61865984000.

Using the calculated size, you can now dump the eMMC. Please note this will take 1-2 minutes.
'''# rkdeveloptool read 0x0 61865984000 ./quartzpro64_emmc_dump.bin'''
Read LBA to file (0%)
...
Read LBA to file (100%)

You now have a full dump of the entire eMMC (SHA256 62cb4ae8d02aeacccf231fa1d00087cdc74b599790a274569305693aa205318d). Note that you can also use the list-partitions and read-partition commands to dump specific partitions, but this only shows GPT partitions on the eMMC. Because of this, it will NOT include the spl_loader found in the first 4MB of the eMMC!

=== Flasing the eMMC ===

Boot the device into maskrom mode, and then verify rkdeveloptool can see the board.
'''# rkdeveloptool list'''
DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=503 Maskrom

Once the board shows up, load the rk3588_spl_loader you downloaded or built earlier, and verify that the eMMC can be seen.
'''# rkdeveloptool boot ./rk3588_spl_loader_v1.08.111.bin'''
Downloading bootloader succeeded.
'''# rkdeveloptool read-flash-info'''
Flash Info:
Manufacturer: SAMSUNG, value=00
Flash Size: 59000 MB
Flash Size: 120832000 Sectors
Block Size: 512 KB
Page Size: 2 KB
ECC Bits: 0
Access Time: 40
Flash CS: Flash<0>

You can now flash the device using either the write command, or write-partition command, depending on what you are trying to do. If you are looking to restore the entire eMMC from a backup you made, you would use the command below to accomplish this.
'''rkdeveloptool write 0 ./quartzpro64_emmc_dump.bin'''

== Ways To Do Things ==

=== To build required components ===

See the Notes projects in the "Collabora RK3588 integration" repository. See in Resources / Misc, below.

=== Using rkdeveloptool ===

Use the [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool PINE64 fork of rkdeveloptool].

Connect a USB-C cable to the "DEBUG PORT" USB-C port, and a second to the "DOWNLOAD" USB-C port. '''Cable direction for the latter matters, so if it doesn't show up after entering download mode, try rotating the USB-C connector to the other side!'''

To enter rockusb mode, interrupt the boot by holding the "V+/REC" on-board button or mashing Ctrl+C very quickly on the serial comms, then type <code>download</code>.

$ rkdeveloptool list

should now show you the device somewhat like this:

'''$ rkdeveloptool list'''
DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=204 Loader

{{Template:note|'''Note:''' If you receive an error about being unable to create the comms object in the following steps, make sure you have the udev rules installed with [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool/-/merge_requests/19 CounterPillow's RK3588 device id patch], install them to <code>/etc/udev/rules.d/</code> and <code>udevadm control --reload</code>}}

Now, we can e.g. show the partitions on the eMMC:

'''$ rkdeveloptool list-partitions'''
# LBA start (sectors) LBA end (sectors) Size (bytes) Name
00 8192 16383 4194304 security
01 16384 24575 4194304 uboot
02 24576 32767 4194304 trust
03 32768 40959 4194304 misc
04 40960 49151 4194304 dtbo
05 49152 51199 1048576 vbmeta
06 51200 133119 41943040 boot
07 133120 329727 100663296 recovery
08 329728 1116159 402653184 backup
09 1116160 1902591 402653184 cache
10 1902592 1935359 16777216 metadata
11 1935360 1937407 1048576 baseparameter
12 1937408 8310783 3263168512 super
13 8310784 120831935 57610829824 userdata

You can now use <code>rkdeveloptool write-partition partitionname yourfile</code> to overwrite one of the eMMC partitions.

=== U-Boot + Kernel On SD, RootFS On eMMC ===

This is the setup [[User:CounterPillow]] currently uses. In short, you'll need a vendor U-Boot on your SD card, with a boot partition on it that contains your <tt>extlinux.conf</tt>, device tree and kernel.

==== Setting Up The SD Card ====

Assuming your SD card is <tt>/dev/sdX</tt>, partition as e.g. follows:

# parted -s /dev/sdX mklabel gpt
# parted -s /dev/sdX mkpart loader 64s 8MiB
# parted -s /dev/sdX mkpart uboot 8MiB 16MiB
# parted -s /dev/sdX mkpart env 16MiB 32MiB
# parted -s /dev/sdX mkpart efi fat32 32MiB 544MiB # increase size as you wish
# parted -s /dev/sdX set 4 boot on

Flash SPL and u-boot:
# dd if=rk3588_spl_loader_v1.06.109.bin of=/dev/sdX1
# dd if=uboot.img of=/dev/sdX2

Then make the filesystem:
# mkfs.vfat -n "efi" /dev/sdX4

Mount it to e.g. <tt>/mnt/sdcardboot</tt>:
# mount /dev/sda4 /mnt/sdcardboot

Put the following in <tt>/mnt/sdcardboot/extlinux/extlinux.conf</tt>:
default l0
menu title QuartzPro64 Boot Menu
prompt 0
timeout 50

label l0
menu label Boot Jank Kernel SDMMC
linux /jank
fdt /dtbs/rockchip/rk3588-evb1-v10.dtb
append earlycon=uart8250,mmio32,0xfeb50000 console=ttyS2,1500000n8 root=/dev/mmcblk0p14 rw rootwait

Copy your kernel to <tt>/mnt/sdcardboot/jank</tt> and your DTB to <tt>/mnt/sdcardboot/dtbs/rockchip/rk3588-evb1-v10.dtb</tt>.

Unmount it, we're done with the SD card.

==== Creating The Root File System ====

First, allocate a file the size of your desired root partition (larger sizes will take longer to transfer, don't make the same mistakes as CounterPillow did), here we choose 16G:
$ fallocate -l 16G rootpart.bin

then, make the filesystem on it. CounterPillow went for ext4 because nobody has ever been fired for using ext4:
$ mkfs.ext4 rootpart.bin

Cool, now mount it:
# mount rootpart.bin /mnt/emmc-root

Now we'll download the Arch Linux ARM generic rootfs tarball and go to town:
$ wget -N http://os.archlinuxarm.org/os/ArchLinuxARM-aarch64-latest.tar.gz{,.sig}
$ curl 'https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x68b3537f39a313b3e574d06777193f152bdbe6a6' | gpg --import=- # in case you're lacking the key
$ gpg --verify ArchLinuxARM-aarch64-latest.tar.gz.sig # don't you dare skip this
# bsdtar -xpf ArchLinuxARM-aarch64-latest.tar.gz -C /mnt/emmc-root # notice that this is run as root

Then we just need to edit fstab. Get the UUID (not PARTUUID) from lsblk:
$ lsblk -o NAME,SIZE,MOUNTPOINTS,UUID

and put it in <tt>/mnt/emmc-root/etc/fstab</tt> as follows:
UUID=''root-uuid-here'' / ext4 defaults 0 1

Unmount <tt>/mnt/emmc-root</tt>, we're done with it.

==== Flashing The Root File System With RockUSB ====

{{Template:warning|This '''will''' destroy whatever data is on that userdata partition. But you're here to run Linux, not Android, right?}}

Plug one USB-C cable into the debug UART port, the other into the download port. Yes you will need two USB-C cables (or A-to-C cables) for this, get over it.

Plug in your board, reset it while hammering Ctrl+c on the debug UART until you get into a u-boot command line. Now enter the <code>download</code> command.

If your device doesn't show up in <code>lsusb</code> or <code>rkdeveloptool list</code> command, pull out the download USB-C plug, rotate it axially by 180 Euler degrees, and plug it back in.

Next, flash the partition. Depending on the size of it, this can take over an hour:
$ rkdeveloptool write-partition userdata rootpart.bin

==== Booting ====

Unplug the download USB-C cable once done.

Put the SD card in the board. Reset it. You can now boot and your rootfs on eMMC will be mounted and contains an ALARM userland.

To update kernels or the device tree, just shut down the board, take out the SD card, write a new kernel or dtb to it, and plug it back in. No more need for rkdeveloptool, yay.

== Resources ==

=== Kernel ===

* [http://lists.infradead.org/pipermail/linux-rockchip/ The linux-rockchip mailing list archives]
* [https://patchwork.kernel.org/project/linux-rockchip/list/ The linux-rockchip patchwork]
* [https://github.com/rockchip-linux/kernel Rockchip BSP kernel tree]
* [https://github.com/radxa/kernel/tree/stable-5.10-rock5 Radxa kernel tree]

=== Misc ===

* The quartz64 and quartz-dev channels on the PINE64 chats (bridged IRC, Matrix, Discord and Telegram)
* [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool PINE64 rkdeveloptool fork]
* [https://github.com/rockchip-linux/rkbin/ Rockchip binary blobs repository]
* [https://opensource.rock-chips.com/wiki_Main_Page Rockchip OpenSource wiki]
* [https://github.com/collabora/rockchiprs rockchiprs] (rkdeveloptool replacement written in Rust)
* [https://gitlab.collabora.com/hardware-enablement/rockchip-3588 Collabora RK3588 integration (u-boot, kernel, Status table, etc.)] - A lot of good information is here

=== Documentation ===

The documentation for the QuartzPro64 board and most of the documentation for the chips it uses hasn't been publicly released yet, but if you do own a QuartzPro64 board, [[User:CounterPillow|CounterPillow]] or [[User:Dsimic|dsimic]] will happily provide the documentation to you for the research or development purposes, if you ask them in the PINE64 [[Main Page#Chat Platforms|chat channels]]. We've got the following documents, some of which can also be found elsewhere on the Internet rather easily:

* RK3588 datasheet
* RK3588 technical reference manual (TRM), parts 1 and 2
* RK3588 hardware design guide, machine translated to English from Chinese, and the original version in Chinese
* RK860 datasheet, including register descriptions
* RK806 datasheet, including register descriptions
* [https://devzone.pine64.org/uploads/d392f228-d53b-11ec-9ab8-fe0395c0c83d/9fee695f-39a4-4858-a58a-c91b86d4fa2c/QuartzPro64-DevBoard-Schematic-V1.0_20220216.pdf QuartzPro64 schematics]
* [https://devzone.pine64.org/uploads/d392f228-d53b-11ec-9ab8-fe0395c0c83d/cf368836-966e-4c3c-9e0d-04a82a705d45/QuartzPro64-DevBoard-PCB-V1.0_20220216_topplace.pdf QuartzPro64 PCB top layout]
* [https://devzone.pine64.org/uploads/d392f228-d53b-11ec-9ab8-fe0395c0c83d/ec260213-d4f7-4c61-ad1f-40ee7b7b7a35/QuartzPro64-DevBoard-PCB-V1.0_20220216_bottomplace.pdf QuartzPro64 PCB bottom layout]
* [https://datasheet.lcsc.com/lcsc/2203311530_AMPAK-Tech-AP6275PR3_C2984106.pdf AMPAK AP6275PR3 (WiFi + BT module) datasheet]
* AMPAK AP6275P (WiFi + BT module) datasheet
* [https://dl.xkwy2018.com/downloads/RK3588/01_Official%20Release/01_Common%20Document/Rockchip_RK3588_EVB_User_Guide_V10_EN_0126.pdf Rockchip RK3588 EVB User Guide v1.0], which the QuartzPro64 is based on

[[Category:Rockchip RK3588]]
[[Category:QuartzPro64]]

PineNote

2024-11-26T07:58:28Z

Dsimic: /* UART Dongle */ Ditto

[[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.}}

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.

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
* 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-11-26T07:58:00Z

Dsimic: /* UART Dongle */ Ditto

[[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.}}

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 open up 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.

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
* 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-11-26T07:57:09Z

Dsimic: /* UART Dongle */ Small wording cleanups

[[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.}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter 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-installed operating system runs 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.

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
* 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-11-26T07:56:00Z

Dsimic: /* UART Dongle */ Linking might help with understanding

[[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.}}

The USB [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter 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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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
* 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]]

PineTab2

2024-11-25T03:49:00Z

Dsimic: /* Keyboard cover */ Wording improvements

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes the following items:

* The PineTab2
* Short [[:File:Pinetab2 quick start guide en ger fr pl final.pdf|user guide]]
* Power cable
* The UART adapter board

Note that the UART adapter is in the same package as the power cable, in a second compartment, and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

{{Warning|It has been reported that the keyboard cover may slide around a bit when the PineTab is stowed in a backpack, for example, causing the built-in hall sensor to misinterpret that as if the cover was opened, causing the suspended PineTab2 to resume and drain the battery. You may want to disable the hall sensor as a wakeup source.}}

When connecting the keyboard cover to the PineTab2, ensure that the camera and the golden pogo pin connectors are correctly aligned. The keyboard cover has five connection pins (the golden "fingers"), out of which four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* WiFi/Bluetooth chip BES2600:
** The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]]. There are at least two code releases available, with two respective/non-interchangeable firmware versions. The latest danctnix kernel has a pretty well working wifi driver.
** The BES2600 Bluetooth driver needs to be implemented.
** Hardware bugs - the power and reset circuitry is not properly implemented in the circuitry, so hard reset of the chip (in the theoretical case it freezes) is impossible without power cycling the whole board.
* The camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMC 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]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

LCD panel:

* [[:File:Boe-technology-th101mb31ig002-28a-datasheet-v10.pdf|BOE TH101MB31IG002-28A datasheet v1.0]]

== Tutorials and Frequently Asked Questions ==

Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

There's also [[:File:PineTab2_display_panel_disassembly_guide.pdf|PineTab2 disassembly guide]]. The disassembly is a very delicate operation, especially around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PineTab2

2024-11-25T03:03:48Z

Dsimic: /* Keyboard cover */ Described the issues with the hall sensor

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes the following items:

* The PineTab2
* Short [[:File:Pinetab2 quick start guide en ger fr pl final.pdf|user guide]]
* Power cable
* The UART adapter board

Note that the UART adapter is in the same package as the power cable, in a second compartment, and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

{{Warning|It has been reported that the keyboard cover may slide around a bit when the PineTab is stowed in a backpack, for example, causing the built-in hall sensor to misinterpret that as if the cover was opened, causing the suspended PineTab2 to resume and drain the battery. You may want to disable the hall sensor as a wakeup source.}}

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.
The external keyboard has 5 connection pins (the golden pins). four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* WiFi/Bluetooth chip BES2600:
** The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]]. There are at least two code releases available, with two respective/non-interchangeable firmware versions. The latest danctnix kernel has a pretty well working wifi driver.
** The BES2600 Bluetooth driver needs to be implemented.
** Hardware bugs - the power and reset circuitry is not properly implemented in the circuitry, so hard reset of the chip (in the theoretical case it freezes) is impossible without power cycling the whole board.
* The camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMC 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]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

LCD panel:

* [[:File:Boe-technology-th101mb31ig002-28a-datasheet-v10.pdf|BOE TH101MB31IG002-28A datasheet v1.0]]

== Tutorials and Frequently Asked Questions ==

Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

There's also [[:File:PineTab2_display_panel_disassembly_guide.pdf|PineTab2 disassembly guide]]. The disassembly is a very delicate operation, especially around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

ROCK64

2024-11-21T19:08:53Z

Dsimic: /* Information, Schematics and Certifications */ Linked the datasheet

[[File:Rock64.jpg|400px|thumb|right|The ROCK64]]

The '''ROCK64''' is a credit-card size 4K60P HDR Media Board Computer powered by Rockchip RK3328 Quad-Core ARM Cortex A53 64-Bit Processor and supports up to 4GB 1866MHz LPDDR3 memory. It provides an eMMC module socket, MicroSD Card slot, Pi-2 Bus, Pi-P5+ Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices.

It supports many different open source operating systems, such as Android, Debian, and Yocto.

== Software releases ==

Under [[ROCK64 Software Releases]] you will find a complete list of currently supported operating system images, which work with the ROCK64, as well as other related software.

OS build Installation Guide and tools:
* [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
* [https://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
* [https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]
* [https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
* [[ROCK64 MAC Address]]

{| class="wikitable sortable"
! Requirement
! GNU/Linux
! Android/Linux
! Kodi/Linux

|-
| 2160p 30Hz 8bit h264/h265/vp8
| partial? [https://forum.pine64.org/showthread.php?tid=4861&pid=32474#pid32474 1]
| yes
| yes

|-
| UI using GPU
| no
| yes
| yes

|-
| Youtube
| no
| yes
| no

|-
| vp9 / mpeg4 / mpeg2 / 10bit HDR / YCbCr
| no
| yes?
| yes

|}

== Upstreaming Status ==
{{Warning|The data presented in this section requires updating.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
! scope="row" | Video Output
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchipdrm</code>
| With mpv, you'll need to specify something like <code>mpv --gpu-context=drm --drm-connector=1.HDMI-A-1</code> to get it to play back on a VT
|-
! scope="row" | 3D Acceleration
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>lima</code>
| Very recent version recommended for the best experience. Has weird glitches on HDMI output in weston.
|-
! scope="row" | Video Decode
| style="background:LightYellow; text-align:center;"|Linux Staging
| style="background:#F99; text-align:center;"|Broken/Not in ffmpeg
| <code>hantro_vpu</code> and <code>rockchip_vdec</code>, using <code>v4l2-requests</code>
| [https://lore.kernel.org/linux-media/49b1-608d4d00-2b-62afdf80@101971638/ Soon to be moved out of staging], ffmpeg patch set [https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201209202513.27449-3-jonas@kwiboo.se/ seemingly abandoned], does not work on newer kernels. [https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-master-stable Git branch with commits]
|-
! scope="row" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>snd_soc_rockchip_*</code>
|-
! scope="row" | Power Button
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk805_pwrkey</code>
| If your PWR switch does nothing unless held, this may need to be loaded manually with <code>modprobe</code> or by putting it in <code>/etc/modules-load.d/</code>
|-
! scope="row" | Analog Video Output
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip_drm_tve</code>
| Definitely needs some cleanup before it'd be ready for mainline, and needs some dt bindings written.
|}

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328]
[[File:Rockchip_RK3328.png|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core Cortex-A53 up to 1.5GHz CPU]
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Unified system L2 cache
* Includes VFP v3 hardware to support single and double-precision operations
* Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
* TrustZone technology support
* Full CoreSight debug solution
* One separate power domain for CPU core system to support internal power switch, and to externally turn on/off based on different application scenario
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
* One isolated voltage domain to support DVFS

==== Frequencies & Voltages ====

{| class="wikitable"
! Frequency
! Voltage
|- style="text-align:right;"
| 408 MHz
| 0.950 V
|- style="text-align:right;"
| 600 MHz
| 0.950 V
|- style="text-align:right;"
| 816 MHz
| 1.000 V
|- style="text-align:right;"
| 1008 MHz
| 1.100 V
|- style="text-align:right;"
| 1200 MHz
| 1.225 V
|- style="text-align:right;"
| 1296 MHz
| 1.300 V
|}

==== Power Draw ====

These numbers for power draw have been measured through an USB power monitor (FNB38) while running the <code>stress</code> utility, whereby "cpu" stands for <code>stress --cpu 4</code> and "vm" stands for <code>stress --vm 4</code>. The former spins on the CPU, the latter stresses the memory. Real workloads are usually a mix of both. The tests were ran through ssh, with nothing besides power and ethernet plugged into the ROCK64

Please keep in mind that under real world usage, many other factors come into play. Having a display connected, running a graphical session, I/O and most importantly the connected USB peripherals can add a lot.

Helpful refresher on the formula for power (W) on DC: power = current × voltage, because the power factor is 1. The ROCK64 runs on 5V, so use that to calculate current if you need to.

{| class="wikitable"
! Frequency
! Power cpu
! Power vm
|- style="text-align:right;"
| 1296 MHz
| 2.64 W
| 2.95 W
|- style="text-align:right;"
| 1200 MHz
| 2.32 W
| 2.69 W
|- style="text-align:right;"
| 1008 MHz
| 1.90 W
| 2.31 W
|- style="text-align:right;"
| 816 MHz
| 1.62 W
| 2.05 W
|- style="text-align:right;"
| 600 MHz
| 1.45 W
| 1.85 W
|- style="text-align:right;"
| 408 MHz
| 1.33 W
| 1.72 W
|- style="text-align:right;"
| Idle (no load)
|colspan="2" style="text-align:center;"| 1.10 W
|}

It appears a good upper bound for a headless setup is in the neighbourhood of 3 W, or the energy contained in 0.025 bananas per hour.

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-450.php ARM Mali-450MP2 Dual-core GPU]
* OpenGL ES 1.1 and 2.0, OpenVG1.1

=== System Memory ===
* LPDDR3 RAM Memory Variants: 1GB, 2GB and 4GB.

== Board Features ==
[[File:ROCK64_sideimg.jpg|400px|thumb|right|The ROCK64 and a size comparison]]

=== Video ===
* Digital Video output up to 4K@60Hz
* 4K HDR @ 60fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===
* 3.5mm A/V Jack (Composite Video Output and RCA Stereo support using conversion cable)

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional USB dongle)

=== Storage ===
[[File:Rock64-emmc-disable-jumper.png|250px|thumb|right|Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red)]]

* microSD - bootable, supports SDHC and SDXC and storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable? Usually accessible as a [http://linux-mtd.infradead.org/doc/general.html Linux MTD] device at <code>/dev/mtd0</code>
* 1 USB3.0 Dedicated Host port
* 2 USB2.0 Dedicated Host port (top one is USB-OTG)

Optionally installed eMMC module can be disabled by placing a jumper onto the two pins on the separate two-pin header, located near one of the mounting holes and two side-mounted buttons. See the picture in this section, in which this two-pin header is highlighted in red.

=== Expansion Ports ===
All GPIO pins, including UART, operate at 3.3V. (See VCCIO5 in the schematics.)

* 2x20 pins "Pi2" GPIO Header
* 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)

== Information, Schematics and Certifications ==
{{Warning|While it's also possible to power the ROCK64 from the pins on the GPIO header, doing that isn't advisable because the [[:File:Murata-manufacturing-blm18pg181sn1-datasheet-r2024.pdf|Murata BLM18PG181SN1]] inductor that's placed in series with that power input is rated for up to 1.5 A when the temperature of its case is below 85 oC. If you can guarantee not to go above those ratings, it may work reliably, otherwise you risk damage to your board.}}

Board dimensions: 85 x 56 x 18.8 mm, see the [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf ROCK64 board dimension drawing]

Power input: 3 A at 5 V DC, using 3.5 mm OD / 1.35 mm ID type H barrel connector (also known as DC 35135, 2 A at 5 V will work if there is no heavy load on the USB 3.0 port)

ROCK64 ver 3.0 SBC related info:
* [https://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf ROCK64 SBC v3.0 Change Notice]
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v3.0_20181105.pdf ROCK64 Schematic v3.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_top_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (top layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_bottom_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (bottom layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_V3_Pi-2_and_Pi-P5+_Bus.pdf ROCK64 SBC v3.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://files.pine64.org/doc/rock64/R64V3%20RTC%20Batt%20connector.png ROCK64 Rev3 SBC RTC Battery Connector polarity]

ROCK64 ver 2.0 SBC related info:
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v2.0_20171019.pdf ROCK64 Schematic v2.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_Pi-2%20_and_Pi_P5+_Bus.pdf ROCK64 SBC v2.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://github.com/Leapo/Rock64-R64.GPIO Github on ROCK64 GPIO library, thanks to Leapo]
* [http://synfare.com/599N105E/hwdocs/rock64/index.html Good documentation about ROCK64 GPIO pins article]
* [https://files.pine64.org/doc/rock64/ROCK64_ES9023_Audio_100Mbps_Ethernet_Board.pdf ROCK64 Audio DAC with 10/100Mbps Ethernet POT Board Schematic]

ROCK64 3D autodesk drawing (from ''TeaPack''):
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e818b9e1b31b54545?viewState=NoIgbgDAdAjCA0IAsSDMAzAnAQwCaoFoYBjAdhgICNTVcCA2S9AJgIFMJTsAOGTU3LmLYQAXSA ROCK64 board 2D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e6078b748ecd478e1?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0AmAEwGYZOAI0G4AtAA4ArABZeo6eIiNRggJwxuomAHYAxoOm6YMaQDZOvNAF8QAXSA ROCK64 board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e45a87155aecc813f?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0BWAYwgGYYAEyEBaQQDYARoJEAWfjMmzckkQCYAHCs5LZAMxi41aAL4gAukA ROCK64 Audio DAC with 10/100Mbps Ethernet POT board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761ee09b497ae3f2f72e?viewState=NoIgbgDAdAjCA0IBmSYEMAcBmAbBgtACwBGhMRATMeQKYYYX5ICcAJhjYWjDBGgKwgAukA ROCK64 board with Audio DAC POT board 3D drawing @courtesy of TeaPack]

Certifications:
* [https://files.pine64.org/doc/cert/ROCK64%20FCC%20certification%20VOC20171129.pdf ROCK64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20CE%20certification%20VOC20171129.pdf ROCK64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20ROHS%20certification%20VOC20170927.pdf ROCK64 RoHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3328 SoC information:
* [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328 SoC Brief]
* [https://rockchip.fr/RK3328%20datasheet%20V1.2.pdf Rockchip RK3328 Datasheet V1.2]
* [https://opensource.rock-chips.com/images/9/97/Rockchip_RK3328TRM_V1.1-Part1-20170321.pdf Rockchip RK3328 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf Rockchip RK805 Datasheet V1.1]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]
* [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]
* [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]

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

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Ethernet related info:
* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* [https://files.pine64.org/doc/rock64/DGKYD111B096GWA1D.pdf 10/100Mbps MegJack on Audio DAC POT board Datasheet]

Peripheral related info:
* [https://files.pine64.org/doc/rock64/PDS-16002%20JMS578%20Datasheet%20(Rev.%201.01).pdf JMicron JMS578 to SATA Datasheet]

Enclosure information:
* [https://files.pine64.org/doc/datasheet/case/ROCK64%20Aluminum%20Waterproof%20Die%20Cast%20Casing.pdf Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]

Remote control button mapping:
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Enclosures ==

[[File:Rock64-Al-Case1-1.jpg|thumb|100px]]

The ROCK64 fits in three officially sold cases.

* [["Model B" Acrylic Open Enclosure]], [https://pine64.com/product/model-b-acrylic-open-enclosure/ Store]
* "Model B" Aluminum Waterproof Enclosure, [https://pine64.com/product/model-b-aluminum-waterproof-enclosure/ Store]
* [[ROCK64 Premium Aluminum Casing]], [https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66 Store]

== Troubleshooting ==

=== HDMI output disconnects as soon as it connects ===

Some older monitors seemingly can get into a weird state wherein the ROCK64 is unable to establish a proper connection with them. [[User:CounterPillow]] has seen this happen on an iiyama ProLite G2773HS connected over HDMI, and an Acer P225HQL connected over an HDMI to DVI adapter. The symptoms usually are that you see the monitor briefly turn on its backlight without displaying a picture, but then immediately either shutting off again or showing a "No Signal" message.

The solution is to completely power down your ROCK64, also removing its power source. Then plug in the monitor, and start up the ROCK64 afterwards. You should now be getting a picture again.

=== Power button doesn't do anything on a short press (Linux) ===

Make sure the <code>rk805_pwrkey</code> module is loaded, e.g. with <code>lsmod | grep rk805_pwrkey</code>. The module auto loading of <code>rk805_pwrkey</code> was fixed in the following upstream kernels: v6.0/v5.15.66/v5.10.142/v5.4.213/v4.19.258/v4.14.293 so there should be no requirement for fixes with those kernels or newer. If it doesn't show up, do a <code>modprobe rk805_pwrkey</code> as root. To make this persistent, create a <code>99-rk805_pwrkey.conf</code> in <code>/etc/modules-load.d/</code> with the content <code>rk805_pwrkey</code>

If it still doesn't work, make sure your init system is actually listening to the button press. With systemd, check <code>/etc/systemd/logind.conf</code> and make sure it's either all commented out (uses defaults) or contains something like <code>HandlePowerKey=poweroff</code>. You can change the short press action by setting <code>HandlePowerKey</code> to one of "ignore", "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", "hybrid-sleep", "suspend-then-hibernate", or "lock".

=== Video output is glitchy during activity ===

If your video output glitches out while there is memory bandwidth pressure, the likely reason is that the video output (VOP) quality-of-service (QoS) registers aren't set to high priority mode.

[[User:CounterPillow]] submitted [https://overviewer.org/~pillow/up/c5179dcb67/0001-rockchip-rk3328-Set-VOP-QoS-to-high-priority.patch a patch] to u-boot to fix this, but someone still needs to write a kernel patch to save/restore the QoS registers from the power domain driver.

== Other Resources ==
* [https://forum.pine64.org/forumdisplay.php?fid=85 ROCK64 Forum]
* IRC Server: irc.pine64.org Channel: ROCK64
* [https://github.com/rock64-linux ROCK64 Linux GitHub Repo]
* [https://github.com/ayufan-rock64 ROCK64 ayufan GitHub Repo]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://github.com/JamesLinEngineer/RKMC Rockchip Android RKMC (Forked from Kodi 16.1)]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* [https://www.armbian.com/rock64 Armbian's ROCK64 Page]

[[Category:ROCK64]] [[Category:Rockchip RK3328]]

File:Murata-manufacturing-blm18pg181sn1-datasheet-r2024.pdf

2024-11-21T19:07:23Z

Dsimic: Murata BLM18PG181SN1 inductor datasheet

== Summary ==
Murata BLM18PG181SN1 inductor datasheet

ROCK64

2024-11-21T18:47:38Z

Dsimic: /* Information, Schematics and Certifications */ Ditto

[[File:Rock64.jpg|400px|thumb|right|The ROCK64]]

The '''ROCK64''' is a credit-card size 4K60P HDR Media Board Computer powered by Rockchip RK3328 Quad-Core ARM Cortex A53 64-Bit Processor and supports up to 4GB 1866MHz LPDDR3 memory. It provides an eMMC module socket, MicroSD Card slot, Pi-2 Bus, Pi-P5+ Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices.

It supports many different open source operating systems, such as Android, Debian, and Yocto.

== Software releases ==

Under [[ROCK64 Software Releases]] you will find a complete list of currently supported operating system images, which work with the ROCK64, as well as other related software.

OS build Installation Guide and tools:
* [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
* [https://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
* [https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]
* [https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
* [[ROCK64 MAC Address]]

{| class="wikitable sortable"
! Requirement
! GNU/Linux
! Android/Linux
! Kodi/Linux

|-
| 2160p 30Hz 8bit h264/h265/vp8
| partial? [https://forum.pine64.org/showthread.php?tid=4861&pid=32474#pid32474 1]
| yes
| yes

|-
| UI using GPU
| no
| yes
| yes

|-
| Youtube
| no
| yes
| no

|-
| vp9 / mpeg4 / mpeg2 / 10bit HDR / YCbCr
| no
| yes?
| yes

|}

== Upstreaming Status ==
{{Warning|The data presented in this section requires updating.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
! scope="row" | Video Output
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchipdrm</code>
| With mpv, you'll need to specify something like <code>mpv --gpu-context=drm --drm-connector=1.HDMI-A-1</code> to get it to play back on a VT
|-
! scope="row" | 3D Acceleration
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>lima</code>
| Very recent version recommended for the best experience. Has weird glitches on HDMI output in weston.
|-
! scope="row" | Video Decode
| style="background:LightYellow; text-align:center;"|Linux Staging
| style="background:#F99; text-align:center;"|Broken/Not in ffmpeg
| <code>hantro_vpu</code> and <code>rockchip_vdec</code>, using <code>v4l2-requests</code>
| [https://lore.kernel.org/linux-media/49b1-608d4d00-2b-62afdf80@101971638/ Soon to be moved out of staging], ffmpeg patch set [https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201209202513.27449-3-jonas@kwiboo.se/ seemingly abandoned], does not work on newer kernels. [https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-master-stable Git branch with commits]
|-
! scope="row" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>snd_soc_rockchip_*</code>
|-
! scope="row" | Power Button
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk805_pwrkey</code>
| If your PWR switch does nothing unless held, this may need to be loaded manually with <code>modprobe</code> or by putting it in <code>/etc/modules-load.d/</code>
|-
! scope="row" | Analog Video Output
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip_drm_tve</code>
| Definitely needs some cleanup before it'd be ready for mainline, and needs some dt bindings written.
|}

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328]
[[File:Rockchip_RK3328.png|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core Cortex-A53 up to 1.5GHz CPU]
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Unified system L2 cache
* Includes VFP v3 hardware to support single and double-precision operations
* Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
* TrustZone technology support
* Full CoreSight debug solution
* One separate power domain for CPU core system to support internal power switch, and to externally turn on/off based on different application scenario
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
* One isolated voltage domain to support DVFS

==== Frequencies & Voltages ====

{| class="wikitable"
! Frequency
! Voltage
|- style="text-align:right;"
| 408 MHz
| 0.950 V
|- style="text-align:right;"
| 600 MHz
| 0.950 V
|- style="text-align:right;"
| 816 MHz
| 1.000 V
|- style="text-align:right;"
| 1008 MHz
| 1.100 V
|- style="text-align:right;"
| 1200 MHz
| 1.225 V
|- style="text-align:right;"
| 1296 MHz
| 1.300 V
|}

==== Power Draw ====

These numbers for power draw have been measured through an USB power monitor (FNB38) while running the <code>stress</code> utility, whereby "cpu" stands for <code>stress --cpu 4</code> and "vm" stands for <code>stress --vm 4</code>. The former spins on the CPU, the latter stresses the memory. Real workloads are usually a mix of both. The tests were ran through ssh, with nothing besides power and ethernet plugged into the ROCK64

Please keep in mind that under real world usage, many other factors come into play. Having a display connected, running a graphical session, I/O and most importantly the connected USB peripherals can add a lot.

Helpful refresher on the formula for power (W) on DC: power = current × voltage, because the power factor is 1. The ROCK64 runs on 5V, so use that to calculate current if you need to.

{| class="wikitable"
! Frequency
! Power cpu
! Power vm
|- style="text-align:right;"
| 1296 MHz
| 2.64 W
| 2.95 W
|- style="text-align:right;"
| 1200 MHz
| 2.32 W
| 2.69 W
|- style="text-align:right;"
| 1008 MHz
| 1.90 W
| 2.31 W
|- style="text-align:right;"
| 816 MHz
| 1.62 W
| 2.05 W
|- style="text-align:right;"
| 600 MHz
| 1.45 W
| 1.85 W
|- style="text-align:right;"
| 408 MHz
| 1.33 W
| 1.72 W
|- style="text-align:right;"
| Idle (no load)
|colspan="2" style="text-align:center;"| 1.10 W
|}

It appears a good upper bound for a headless setup is in the neighbourhood of 3 W, or the energy contained in 0.025 bananas per hour.

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-450.php ARM Mali-450MP2 Dual-core GPU]
* OpenGL ES 1.1 and 2.0, OpenVG1.1

=== System Memory ===
* LPDDR3 RAM Memory Variants: 1GB, 2GB and 4GB.

== Board Features ==
[[File:ROCK64_sideimg.jpg|400px|thumb|right|The ROCK64 and a size comparison]]

=== Video ===
* Digital Video output up to 4K@60Hz
* 4K HDR @ 60fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===
* 3.5mm A/V Jack (Composite Video Output and RCA Stereo support using conversion cable)

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional USB dongle)

=== Storage ===
[[File:Rock64-emmc-disable-jumper.png|250px|thumb|right|Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red)]]

* microSD - bootable, supports SDHC and SDXC and storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable? Usually accessible as a [http://linux-mtd.infradead.org/doc/general.html Linux MTD] device at <code>/dev/mtd0</code>
* 1 USB3.0 Dedicated Host port
* 2 USB2.0 Dedicated Host port (top one is USB-OTG)

Optionally installed eMMC module can be disabled by placing a jumper onto the two pins on the separate two-pin header, located near one of the mounting holes and two side-mounted buttons. See the picture in this section, in which this two-pin header is highlighted in red.

=== Expansion Ports ===
All GPIO pins, including UART, operate at 3.3V. (See VCCIO5 in the schematics.)

* 2x20 pins "Pi2" GPIO Header
* 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)

== Information, Schematics and Certifications ==
{{Warning|While it's also possible to power the ROCK64 from the pins on the GPIO header, doing that isn't advisable because the inductor that's placed in series with that power input is rated for up to 1.5 A when the temperature of its case is below 85 oC. If you can guarantee not to go above those ratings, it may work reliably, otherwise you risk damage to your board.}}

Board dimensions: 85 x 56 x 18.8 mm, see the [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf ROCK64 board dimension drawing]

Power input: 3 A at 5 V DC, using 3.5 mm OD / 1.35 mm ID type H barrel connector (also known as DC 35135, 2 A at 5 V will work if there is no heavy load on the USB 3.0 port)

ROCK64 ver 3.0 SBC related info:
* [https://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf ROCK64 SBC v3.0 Change Notice]
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v3.0_20181105.pdf ROCK64 Schematic v3.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_top_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (top layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_bottom_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (bottom layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_V3_Pi-2_and_Pi-P5+_Bus.pdf ROCK64 SBC v3.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://files.pine64.org/doc/rock64/R64V3%20RTC%20Batt%20connector.png ROCK64 Rev3 SBC RTC Battery Connector polarity]

ROCK64 ver 2.0 SBC related info:
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v2.0_20171019.pdf ROCK64 Schematic v2.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_Pi-2%20_and_Pi_P5+_Bus.pdf ROCK64 SBC v2.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://github.com/Leapo/Rock64-R64.GPIO Github on ROCK64 GPIO library, thanks to Leapo]
* [http://synfare.com/599N105E/hwdocs/rock64/index.html Good documentation about ROCK64 GPIO pins article]
* [https://files.pine64.org/doc/rock64/ROCK64_ES9023_Audio_100Mbps_Ethernet_Board.pdf ROCK64 Audio DAC with 10/100Mbps Ethernet POT Board Schematic]

ROCK64 3D autodesk drawing (from ''TeaPack''):
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e818b9e1b31b54545?viewState=NoIgbgDAdAjCA0IAsSDMAzAnAQwCaoFoYBjAdhgICNTVcCA2S9AJgIFMJTsAOGTU3LmLYQAXSA ROCK64 board 2D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e6078b748ecd478e1?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0AmAEwGYZOAI0G4AtAA4ArABZeo6eIiNRggJwxuomAHYAxoOm6YMaQDZOvNAF8QAXSA ROCK64 board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e45a87155aecc813f?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0BWAYwgGYYAEyEBaQQDYARoJEAWfjMmzckkQCYAHCs5LZAMxi41aAL4gAukA ROCK64 Audio DAC with 10/100Mbps Ethernet POT board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761ee09b497ae3f2f72e?viewState=NoIgbgDAdAjCA0IBmSYEMAcBmAbBgtACwBGhMRATMeQKYYYX5ICcAJhjYWjDBGgKwgAukA ROCK64 board with Audio DAC POT board 3D drawing @courtesy of TeaPack]

Certifications:
* [https://files.pine64.org/doc/cert/ROCK64%20FCC%20certification%20VOC20171129.pdf ROCK64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20CE%20certification%20VOC20171129.pdf ROCK64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20ROHS%20certification%20VOC20170927.pdf ROCK64 RoHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3328 SoC information:
* [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328 SoC Brief]
* [https://rockchip.fr/RK3328%20datasheet%20V1.2.pdf Rockchip RK3328 Datasheet V1.2]
* [https://opensource.rock-chips.com/images/9/97/Rockchip_RK3328TRM_V1.1-Part1-20170321.pdf Rockchip RK3328 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf Rockchip RK805 Datasheet V1.1]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]
* [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]
* [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]

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

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Ethernet related info:
* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* [https://files.pine64.org/doc/rock64/DGKYD111B096GWA1D.pdf 10/100Mbps MegJack on Audio DAC POT board Datasheet]

Peripheral related info:
* [https://files.pine64.org/doc/rock64/PDS-16002%20JMS578%20Datasheet%20(Rev.%201.01).pdf JMicron JMS578 to SATA Datasheet]

Enclosure information:
* [https://files.pine64.org/doc/datasheet/case/ROCK64%20Aluminum%20Waterproof%20Die%20Cast%20Casing.pdf Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]

Remote control button mapping:
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Enclosures ==

[[File:Rock64-Al-Case1-1.jpg|thumb|100px]]

The ROCK64 fits in three officially sold cases.

* [["Model B" Acrylic Open Enclosure]], [https://pine64.com/product/model-b-acrylic-open-enclosure/ Store]
* "Model B" Aluminum Waterproof Enclosure, [https://pine64.com/product/model-b-aluminum-waterproof-enclosure/ Store]
* [[ROCK64 Premium Aluminum Casing]], [https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66 Store]

== Troubleshooting ==

=== HDMI output disconnects as soon as it connects ===

Some older monitors seemingly can get into a weird state wherein the ROCK64 is unable to establish a proper connection with them. [[User:CounterPillow]] has seen this happen on an iiyama ProLite G2773HS connected over HDMI, and an Acer P225HQL connected over an HDMI to DVI adapter. The symptoms usually are that you see the monitor briefly turn on its backlight without displaying a picture, but then immediately either shutting off again or showing a "No Signal" message.

The solution is to completely power down your ROCK64, also removing its power source. Then plug in the monitor, and start up the ROCK64 afterwards. You should now be getting a picture again.

=== Power button doesn't do anything on a short press (Linux) ===

Make sure the <code>rk805_pwrkey</code> module is loaded, e.g. with <code>lsmod | grep rk805_pwrkey</code>. The module auto loading of <code>rk805_pwrkey</code> was fixed in the following upstream kernels: v6.0/v5.15.66/v5.10.142/v5.4.213/v4.19.258/v4.14.293 so there should be no requirement for fixes with those kernels or newer. If it doesn't show up, do a <code>modprobe rk805_pwrkey</code> as root. To make this persistent, create a <code>99-rk805_pwrkey.conf</code> in <code>/etc/modules-load.d/</code> with the content <code>rk805_pwrkey</code>

If it still doesn't work, make sure your init system is actually listening to the button press. With systemd, check <code>/etc/systemd/logind.conf</code> and make sure it's either all commented out (uses defaults) or contains something like <code>HandlePowerKey=poweroff</code>. You can change the short press action by setting <code>HandlePowerKey</code> to one of "ignore", "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", "hybrid-sleep", "suspend-then-hibernate", or "lock".

=== Video output is glitchy during activity ===

If your video output glitches out while there is memory bandwidth pressure, the likely reason is that the video output (VOP) quality-of-service (QoS) registers aren't set to high priority mode.

[[User:CounterPillow]] submitted [https://overviewer.org/~pillow/up/c5179dcb67/0001-rockchip-rk3328-Set-VOP-QoS-to-high-priority.patch a patch] to u-boot to fix this, but someone still needs to write a kernel patch to save/restore the QoS registers from the power domain driver.

== Other Resources ==
* [https://forum.pine64.org/forumdisplay.php?fid=85 ROCK64 Forum]
* IRC Server: irc.pine64.org Channel: ROCK64
* [https://github.com/rock64-linux ROCK64 Linux GitHub Repo]
* [https://github.com/ayufan-rock64 ROCK64 ayufan GitHub Repo]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://github.com/JamesLinEngineer/RKMC Rockchip Android RKMC (Forked from Kodi 16.1)]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* [https://www.armbian.com/rock64 Armbian's ROCK64 Page]

[[Category:ROCK64]] [[Category:Rockchip RK3328]]

ROCK64

2024-11-21T18:46:57Z

Dsimic: /* Information, Schematics and Certifications */ Wording improvements

[[File:Rock64.jpg|400px|thumb|right|The ROCK64]]

The '''ROCK64''' is a credit-card size 4K60P HDR Media Board Computer powered by Rockchip RK3328 Quad-Core ARM Cortex A53 64-Bit Processor and supports up to 4GB 1866MHz LPDDR3 memory. It provides an eMMC module socket, MicroSD Card slot, Pi-2 Bus, Pi-P5+ Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices.

It supports many different open source operating systems, such as Android, Debian, and Yocto.

== Software releases ==

Under [[ROCK64 Software Releases]] you will find a complete list of currently supported operating system images, which work with the ROCK64, as well as other related software.

OS build Installation Guide and tools:
* [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
* [https://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
* [https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]
* [https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
* [[ROCK64 MAC Address]]

{| class="wikitable sortable"
! Requirement
! GNU/Linux
! Android/Linux
! Kodi/Linux

|-
| 2160p 30Hz 8bit h264/h265/vp8
| partial? [https://forum.pine64.org/showthread.php?tid=4861&pid=32474#pid32474 1]
| yes
| yes

|-
| UI using GPU
| no
| yes
| yes

|-
| Youtube
| no
| yes
| no

|-
| vp9 / mpeg4 / mpeg2 / 10bit HDR / YCbCr
| no
| yes?
| yes

|}

== Upstreaming Status ==
{{Warning|The data presented in this section requires updating.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
! scope="row" | Video Output
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchipdrm</code>
| With mpv, you'll need to specify something like <code>mpv --gpu-context=drm --drm-connector=1.HDMI-A-1</code> to get it to play back on a VT
|-
! scope="row" | 3D Acceleration
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>lima</code>
| Very recent version recommended for the best experience. Has weird glitches on HDMI output in weston.
|-
! scope="row" | Video Decode
| style="background:LightYellow; text-align:center;"|Linux Staging
| style="background:#F99; text-align:center;"|Broken/Not in ffmpeg
| <code>hantro_vpu</code> and <code>rockchip_vdec</code>, using <code>v4l2-requests</code>
| [https://lore.kernel.org/linux-media/49b1-608d4d00-2b-62afdf80@101971638/ Soon to be moved out of staging], ffmpeg patch set [https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201209202513.27449-3-jonas@kwiboo.se/ seemingly abandoned], does not work on newer kernels. [https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-master-stable Git branch with commits]
|-
! scope="row" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>snd_soc_rockchip_*</code>
|-
! scope="row" | Power Button
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk805_pwrkey</code>
| If your PWR switch does nothing unless held, this may need to be loaded manually with <code>modprobe</code> or by putting it in <code>/etc/modules-load.d/</code>
|-
! scope="row" | Analog Video Output
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip_drm_tve</code>
| Definitely needs some cleanup before it'd be ready for mainline, and needs some dt bindings written.
|}

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328]
[[File:Rockchip_RK3328.png|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core Cortex-A53 up to 1.5GHz CPU]
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Unified system L2 cache
* Includes VFP v3 hardware to support single and double-precision operations
* Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
* TrustZone technology support
* Full CoreSight debug solution
* One separate power domain for CPU core system to support internal power switch, and to externally turn on/off based on different application scenario
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
* One isolated voltage domain to support DVFS

==== Frequencies & Voltages ====

{| class="wikitable"
! Frequency
! Voltage
|- style="text-align:right;"
| 408 MHz
| 0.950 V
|- style="text-align:right;"
| 600 MHz
| 0.950 V
|- style="text-align:right;"
| 816 MHz
| 1.000 V
|- style="text-align:right;"
| 1008 MHz
| 1.100 V
|- style="text-align:right;"
| 1200 MHz
| 1.225 V
|- style="text-align:right;"
| 1296 MHz
| 1.300 V
|}

==== Power Draw ====

These numbers for power draw have been measured through an USB power monitor (FNB38) while running the <code>stress</code> utility, whereby "cpu" stands for <code>stress --cpu 4</code> and "vm" stands for <code>stress --vm 4</code>. The former spins on the CPU, the latter stresses the memory. Real workloads are usually a mix of both. The tests were ran through ssh, with nothing besides power and ethernet plugged into the ROCK64

Please keep in mind that under real world usage, many other factors come into play. Having a display connected, running a graphical session, I/O and most importantly the connected USB peripherals can add a lot.

Helpful refresher on the formula for power (W) on DC: power = current × voltage, because the power factor is 1. The ROCK64 runs on 5V, so use that to calculate current if you need to.

{| class="wikitable"
! Frequency
! Power cpu
! Power vm
|- style="text-align:right;"
| 1296 MHz
| 2.64 W
| 2.95 W
|- style="text-align:right;"
| 1200 MHz
| 2.32 W
| 2.69 W
|- style="text-align:right;"
| 1008 MHz
| 1.90 W
| 2.31 W
|- style="text-align:right;"
| 816 MHz
| 1.62 W
| 2.05 W
|- style="text-align:right;"
| 600 MHz
| 1.45 W
| 1.85 W
|- style="text-align:right;"
| 408 MHz
| 1.33 W
| 1.72 W
|- style="text-align:right;"
| Idle (no load)
|colspan="2" style="text-align:center;"| 1.10 W
|}

It appears a good upper bound for a headless setup is in the neighbourhood of 3 W, or the energy contained in 0.025 bananas per hour.

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-450.php ARM Mali-450MP2 Dual-core GPU]
* OpenGL ES 1.1 and 2.0, OpenVG1.1

=== System Memory ===
* LPDDR3 RAM Memory Variants: 1GB, 2GB and 4GB.

== Board Features ==
[[File:ROCK64_sideimg.jpg|400px|thumb|right|The ROCK64 and a size comparison]]

=== Video ===
* Digital Video output up to 4K@60Hz
* 4K HDR @ 60fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===
* 3.5mm A/V Jack (Composite Video Output and RCA Stereo support using conversion cable)

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional USB dongle)

=== Storage ===
[[File:Rock64-emmc-disable-jumper.png|250px|thumb|right|Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red)]]

* microSD - bootable, supports SDHC and SDXC and storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable? Usually accessible as a [http://linux-mtd.infradead.org/doc/general.html Linux MTD] device at <code>/dev/mtd0</code>
* 1 USB3.0 Dedicated Host port
* 2 USB2.0 Dedicated Host port (top one is USB-OTG)

Optionally installed eMMC module can be disabled by placing a jumper onto the two pins on the separate two-pin header, located near one of the mounting holes and two side-mounted buttons. See the picture in this section, in which this two-pin header is highlighted in red.

=== Expansion Ports ===
All GPIO pins, including UART, operate at 3.3V. (See VCCIO5 in the schematics.)

* 2x20 pins "Pi2" GPIO Header
* 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)

== Information, Schematics and Certifications ==
{{Warning|While it's also possible to power the ROCK64 from the pins on the GPIO header, doing that isn't advisable because the inductor that's placed in series with that power input is rated for up to 1.5 A when the temperature of its case is below 85 oC. If you can guarantee not to go above those ratings, it may work reliably.}}

Board dimensions: 85 x 56 x 18.8 mm, see the [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf ROCK64 board dimension drawing]

Power input: 3 A at 5 V DC, using 3.5 mm OD / 1.35 mm ID type H barrel connector (also known as DC 35135, 2 A at 5 V will work if there is no heavy load on the USB 3.0 port)

ROCK64 ver 3.0 SBC related info:
* [https://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf ROCK64 SBC v3.0 Change Notice]
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v3.0_20181105.pdf ROCK64 Schematic v3.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_top_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (top layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_bottom_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (bottom layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_V3_Pi-2_and_Pi-P5+_Bus.pdf ROCK64 SBC v3.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://files.pine64.org/doc/rock64/R64V3%20RTC%20Batt%20connector.png ROCK64 Rev3 SBC RTC Battery Connector polarity]

ROCK64 ver 2.0 SBC related info:
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v2.0_20171019.pdf ROCK64 Schematic v2.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_Pi-2%20_and_Pi_P5+_Bus.pdf ROCK64 SBC v2.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://github.com/Leapo/Rock64-R64.GPIO Github on ROCK64 GPIO library, thanks to Leapo]
* [http://synfare.com/599N105E/hwdocs/rock64/index.html Good documentation about ROCK64 GPIO pins article]
* [https://files.pine64.org/doc/rock64/ROCK64_ES9023_Audio_100Mbps_Ethernet_Board.pdf ROCK64 Audio DAC with 10/100Mbps Ethernet POT Board Schematic]

ROCK64 3D autodesk drawing (from ''TeaPack''):
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e818b9e1b31b54545?viewState=NoIgbgDAdAjCA0IAsSDMAzAnAQwCaoFoYBjAdhgICNTVcCA2S9AJgIFMJTsAOGTU3LmLYQAXSA ROCK64 board 2D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e6078b748ecd478e1?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0AmAEwGYZOAI0G4AtAA4ArABZeo6eIiNRggJwxuomAHYAxoOm6YMaQDZOvNAF8QAXSA ROCK64 board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e45a87155aecc813f?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0BWAYwgGYYAEyEBaQQDYARoJEAWfjMmzckkQCYAHCs5LZAMxi41aAL4gAukA ROCK64 Audio DAC with 10/100Mbps Ethernet POT board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761ee09b497ae3f2f72e?viewState=NoIgbgDAdAjCA0IBmSYEMAcBmAbBgtACwBGhMRATMeQKYYYX5ICcAJhjYWjDBGgKwgAukA ROCK64 board with Audio DAC POT board 3D drawing @courtesy of TeaPack]

Certifications:
* [https://files.pine64.org/doc/cert/ROCK64%20FCC%20certification%20VOC20171129.pdf ROCK64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20CE%20certification%20VOC20171129.pdf ROCK64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20ROHS%20certification%20VOC20170927.pdf ROCK64 RoHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3328 SoC information:
* [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328 SoC Brief]
* [https://rockchip.fr/RK3328%20datasheet%20V1.2.pdf Rockchip RK3328 Datasheet V1.2]
* [https://opensource.rock-chips.com/images/9/97/Rockchip_RK3328TRM_V1.1-Part1-20170321.pdf Rockchip RK3328 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf Rockchip RK805 Datasheet V1.1]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]
* [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]
* [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]

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

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Ethernet related info:
* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* [https://files.pine64.org/doc/rock64/DGKYD111B096GWA1D.pdf 10/100Mbps MegJack on Audio DAC POT board Datasheet]

Peripheral related info:
* [https://files.pine64.org/doc/rock64/PDS-16002%20JMS578%20Datasheet%20(Rev.%201.01).pdf JMicron JMS578 to SATA Datasheet]

Enclosure information:
* [https://files.pine64.org/doc/datasheet/case/ROCK64%20Aluminum%20Waterproof%20Die%20Cast%20Casing.pdf Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]

Remote control button mapping:
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Enclosures ==

[[File:Rock64-Al-Case1-1.jpg|thumb|100px]]

The ROCK64 fits in three officially sold cases.

* [["Model B" Acrylic Open Enclosure]], [https://pine64.com/product/model-b-acrylic-open-enclosure/ Store]
* "Model B" Aluminum Waterproof Enclosure, [https://pine64.com/product/model-b-aluminum-waterproof-enclosure/ Store]
* [[ROCK64 Premium Aluminum Casing]], [https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66 Store]

== Troubleshooting ==

=== HDMI output disconnects as soon as it connects ===

Some older monitors seemingly can get into a weird state wherein the ROCK64 is unable to establish a proper connection with them. [[User:CounterPillow]] has seen this happen on an iiyama ProLite G2773HS connected over HDMI, and an Acer P225HQL connected over an HDMI to DVI adapter. The symptoms usually are that you see the monitor briefly turn on its backlight without displaying a picture, but then immediately either shutting off again or showing a "No Signal" message.

The solution is to completely power down your ROCK64, also removing its power source. Then plug in the monitor, and start up the ROCK64 afterwards. You should now be getting a picture again.

=== Power button doesn't do anything on a short press (Linux) ===

Make sure the <code>rk805_pwrkey</code> module is loaded, e.g. with <code>lsmod | grep rk805_pwrkey</code>. The module auto loading of <code>rk805_pwrkey</code> was fixed in the following upstream kernels: v6.0/v5.15.66/v5.10.142/v5.4.213/v4.19.258/v4.14.293 so there should be no requirement for fixes with those kernels or newer. If it doesn't show up, do a <code>modprobe rk805_pwrkey</code> as root. To make this persistent, create a <code>99-rk805_pwrkey.conf</code> in <code>/etc/modules-load.d/</code> with the content <code>rk805_pwrkey</code>

If it still doesn't work, make sure your init system is actually listening to the button press. With systemd, check <code>/etc/systemd/logind.conf</code> and make sure it's either all commented out (uses defaults) or contains something like <code>HandlePowerKey=poweroff</code>. You can change the short press action by setting <code>HandlePowerKey</code> to one of "ignore", "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", "hybrid-sleep", "suspend-then-hibernate", or "lock".

=== Video output is glitchy during activity ===

If your video output glitches out while there is memory bandwidth pressure, the likely reason is that the video output (VOP) quality-of-service (QoS) registers aren't set to high priority mode.

[[User:CounterPillow]] submitted [https://overviewer.org/~pillow/up/c5179dcb67/0001-rockchip-rk3328-Set-VOP-QoS-to-high-priority.patch a patch] to u-boot to fix this, but someone still needs to write a kernel patch to save/restore the QoS registers from the power domain driver.

== Other Resources ==
* [https://forum.pine64.org/forumdisplay.php?fid=85 ROCK64 Forum]
* IRC Server: irc.pine64.org Channel: ROCK64
* [https://github.com/rock64-linux ROCK64 Linux GitHub Repo]
* [https://github.com/ayufan-rock64 ROCK64 ayufan GitHub Repo]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://github.com/JamesLinEngineer/RKMC Rockchip Android RKMC (Forked from Kodi 16.1)]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* [https://www.armbian.com/rock64 Armbian's ROCK64 Page]

[[Category:ROCK64]] [[Category:Rockchip RK3328]]

ROCK64

2024-11-21T18:46:04Z

Dsimic: /* Information, Schematics and Certifications */ Described the GPIO power input

[[File:Rock64.jpg|400px|thumb|right|The ROCK64]]

The '''ROCK64''' is a credit-card size 4K60P HDR Media Board Computer powered by Rockchip RK3328 Quad-Core ARM Cortex A53 64-Bit Processor and supports up to 4GB 1866MHz LPDDR3 memory. It provides an eMMC module socket, MicroSD Card slot, Pi-2 Bus, Pi-P5+ Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices.

It supports many different open source operating systems, such as Android, Debian, and Yocto.

== Software releases ==

Under [[ROCK64 Software Releases]] you will find a complete list of currently supported operating system images, which work with the ROCK64, as well as other related software.

OS build Installation Guide and tools:
* [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
* [https://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
* [https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]
* [https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
* [[ROCK64 MAC Address]]

{| class="wikitable sortable"
! Requirement
! GNU/Linux
! Android/Linux
! Kodi/Linux

|-
| 2160p 30Hz 8bit h264/h265/vp8
| partial? [https://forum.pine64.org/showthread.php?tid=4861&pid=32474#pid32474 1]
| yes
| yes

|-
| UI using GPU
| no
| yes
| yes

|-
| Youtube
| no
| yes
| no

|-
| vp9 / mpeg4 / mpeg2 / 10bit HDR / YCbCr
| no
| yes?
| yes

|}

== Upstreaming Status ==
{{Warning|The data presented in this section requires updating.}}

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
|-
! scope="row" | Video Output
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchipdrm</code>
| With mpv, you'll need to specify something like <code>mpv --gpu-context=drm --drm-connector=1.HDMI-A-1</code> to get it to play back on a VT
|-
! scope="row" | 3D Acceleration
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>lima</code>
| Very recent version recommended for the best experience. Has weird glitches on HDMI output in weston.
|-
! scope="row" | Video Decode
| style="background:LightYellow; text-align:center;"|Linux Staging
| style="background:#F99; text-align:center;"|Broken/Not in ffmpeg
| <code>hantro_vpu</code> and <code>rockchip_vdec</code>, using <code>v4l2-requests</code>
| [https://lore.kernel.org/linux-media/49b1-608d4d00-2b-62afdf80@101971638/ Soon to be moved out of staging], ffmpeg patch set [https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201209202513.27449-3-jonas@kwiboo.se/ seemingly abandoned], does not work on newer kernels. [https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-master-stable Git branch with commits]
|-
! scope="row" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>snd_soc_rockchip_*</code>
|-
! scope="row" | Power Button
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk805_pwrkey</code>
| If your PWR switch does nothing unless held, this may need to be loaded manually with <code>modprobe</code> or by putting it in <code>/etc/modules-load.d/</code>
|-
! scope="row" | Analog Video Output
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip_drm_tve</code>
| Definitely needs some cleanup before it'd be ready for mainline, and needs some dt bindings written.
|}

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328]
[[File:Rockchip_RK3328.png|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core Cortex-A53 up to 1.5GHz CPU]
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Unified system L2 cache
* Includes VFP v3 hardware to support single and double-precision operations
* Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
* TrustZone technology support
* Full CoreSight debug solution
* One separate power domain for CPU core system to support internal power switch, and to externally turn on/off based on different application scenario
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
* One isolated voltage domain to support DVFS

==== Frequencies & Voltages ====

{| class="wikitable"
! Frequency
! Voltage
|- style="text-align:right;"
| 408 MHz
| 0.950 V
|- style="text-align:right;"
| 600 MHz
| 0.950 V
|- style="text-align:right;"
| 816 MHz
| 1.000 V
|- style="text-align:right;"
| 1008 MHz
| 1.100 V
|- style="text-align:right;"
| 1200 MHz
| 1.225 V
|- style="text-align:right;"
| 1296 MHz
| 1.300 V
|}

==== Power Draw ====

These numbers for power draw have been measured through an USB power monitor (FNB38) while running the <code>stress</code> utility, whereby "cpu" stands for <code>stress --cpu 4</code> and "vm" stands for <code>stress --vm 4</code>. The former spins on the CPU, the latter stresses the memory. Real workloads are usually a mix of both. The tests were ran through ssh, with nothing besides power and ethernet plugged into the ROCK64

Please keep in mind that under real world usage, many other factors come into play. Having a display connected, running a graphical session, I/O and most importantly the connected USB peripherals can add a lot.

Helpful refresher on the formula for power (W) on DC: power = current × voltage, because the power factor is 1. The ROCK64 runs on 5V, so use that to calculate current if you need to.

{| class="wikitable"
! Frequency
! Power cpu
! Power vm
|- style="text-align:right;"
| 1296 MHz
| 2.64 W
| 2.95 W
|- style="text-align:right;"
| 1200 MHz
| 2.32 W
| 2.69 W
|- style="text-align:right;"
| 1008 MHz
| 1.90 W
| 2.31 W
|- style="text-align:right;"
| 816 MHz
| 1.62 W
| 2.05 W
|- style="text-align:right;"
| 600 MHz
| 1.45 W
| 1.85 W
|- style="text-align:right;"
| 408 MHz
| 1.33 W
| 1.72 W
|- style="text-align:right;"
| Idle (no load)
|colspan="2" style="text-align:center;"| 1.10 W
|}

It appears a good upper bound for a headless setup is in the neighbourhood of 3 W, or the energy contained in 0.025 bananas per hour.

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-450.php ARM Mali-450MP2 Dual-core GPU]
* OpenGL ES 1.1 and 2.0, OpenVG1.1

=== System Memory ===
* LPDDR3 RAM Memory Variants: 1GB, 2GB and 4GB.

== Board Features ==
[[File:ROCK64_sideimg.jpg|400px|thumb|right|The ROCK64 and a size comparison]]

=== Video ===
* Digital Video output up to 4K@60Hz
* 4K HDR @ 60fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===
* 3.5mm A/V Jack (Composite Video Output and RCA Stereo support using conversion cable)

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional USB dongle)

=== Storage ===
[[File:Rock64-emmc-disable-jumper.png|250px|thumb|right|Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red)]]

* microSD - bootable, supports SDHC and SDXC and storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable? Usually accessible as a [http://linux-mtd.infradead.org/doc/general.html Linux MTD] device at <code>/dev/mtd0</code>
* 1 USB3.0 Dedicated Host port
* 2 USB2.0 Dedicated Host port (top one is USB-OTG)

Optionally installed eMMC module can be disabled by placing a jumper onto the two pins on the separate two-pin header, located near one of the mounting holes and two side-mounted buttons. See the picture in this section, in which this two-pin header is highlighted in red.

=== Expansion Ports ===
All GPIO pins, including UART, operate at 3.3V. (See VCCIO5 in the schematics.)

* 2x20 pins "Pi2" GPIO Header
* 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)

== Information, Schematics and Certifications ==
{{Warning|While it's also possible to power the ROCK64 from the pins on the GPIO header, doing that isn't advisable because the inductor that's placed in series with that power input is rated for up to 1.5 A below 85 oC of its case temperature. If you can guarantee not to go above those ratings, it may work reliably.}}

Board dimensions: 85 x 56 x 18.8 mm, see the [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf ROCK64 board dimension drawing]

Power input: 3 A at 5 V DC, using 3.5 mm OD / 1.35 mm ID type H barrel connector (also known as DC 35135, 2 A at 5 V will work if there is no heavy load on the USB 3.0 port)

ROCK64 ver 3.0 SBC related info:
* [https://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf ROCK64 SBC v3.0 Change Notice]
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v3.0_20181105.pdf ROCK64 Schematic v3.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_top_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (top layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_comp_ref_bottom_v3.0_20181105.pdf ROCK64 Component Reference location v3.0 (bottom layer)]
* [https://files.pine64.org/doc/rock64/ROCK64_V3_Pi-2_and_Pi-P5+_Bus.pdf ROCK64 SBC v3.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://files.pine64.org/doc/rock64/R64V3%20RTC%20Batt%20connector.png ROCK64 Rev3 SBC RTC Battery Connector polarity]

ROCK64 ver 2.0 SBC related info:
* [https://files.pine64.org/doc/rock64/ROCK64_Schematic_v2.0_20171019.pdf ROCK64 Schematic v2.0 (Production Release)]
* [https://files.pine64.org/doc/rock64/ROCK64_Pi-2%20_and_Pi_P5+_Bus.pdf ROCK64 SBC v2.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
* [https://github.com/Leapo/Rock64-R64.GPIO Github on ROCK64 GPIO library, thanks to Leapo]
* [http://synfare.com/599N105E/hwdocs/rock64/index.html Good documentation about ROCK64 GPIO pins article]
* [https://files.pine64.org/doc/rock64/ROCK64_ES9023_Audio_100Mbps_Ethernet_Board.pdf ROCK64 Audio DAC with 10/100Mbps Ethernet POT Board Schematic]

ROCK64 3D autodesk drawing (from ''TeaPack''):
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e818b9e1b31b54545?viewState=NoIgbgDAdAjCA0IAsSDMAzAnAQwCaoFoYBjAdhgICNTVcCA2S9AJgIFMJTsAOGTU3LmLYQAXSA ROCK64 board 2D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e6078b748ecd478e1?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0AmAEwGYZOAI0G4AtAA4ArABZeo6eIiNRggJwxuomAHYAxoOm6YMaQDZOvNAF8QAXSA ROCK64 board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761e45a87155aecc813f?viewState=NoIgbgDAdAjCA0IDeAdEAXAngBwKZoC40ARXAZwEsBzAOzXjQEMyzd1C0BWAYwgGYYAEyEBaQQDYARoJEAWfjMmzckkQCYAHCs5LZAMxi41aAL4gAukA ROCK64 Audio DAC with 10/100Mbps Ethernet POT board 3D drawing @courtesy of TeaPack]
* [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH7f1edQT22b515c761ee09b497ae3f2f72e?viewState=NoIgbgDAdAjCA0IBmSYEMAcBmAbBgtACwBGhMRATMeQKYYYX5ICcAJhjYWjDBGgKwgAukA ROCK64 board with Audio DAC POT board 3D drawing @courtesy of TeaPack]

Certifications:
* [https://files.pine64.org/doc/cert/ROCK64%20FCC%20certification%20VOC20171129.pdf ROCK64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20CE%20certification%20VOC20171129.pdf ROCK64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCK64%20ROHS%20certification%20VOC20170927.pdf ROCK64 RoHS Certificate]

== Datasheets for Components and Peripherals ==

Rockchip RK3328 SoC information:
* [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328 SoC Brief]
* [https://rockchip.fr/RK3328%20datasheet%20V1.2.pdf Rockchip RK3328 Datasheet V1.2]
* [https://opensource.rock-chips.com/images/9/97/Rockchip_RK3328TRM_V1.1-Part1-20170321.pdf Rockchip RK3328 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf Rockchip RK805 Datasheet V1.1]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]
* [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]
* [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]

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

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Ethernet related info:
* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* [https://files.pine64.org/doc/rock64/DGKYD111B096GWA1D.pdf 10/100Mbps MegJack on Audio DAC POT board Datasheet]

Peripheral related info:
* [https://files.pine64.org/doc/rock64/PDS-16002%20JMS578%20Datasheet%20(Rev.%201.01).pdf JMicron JMS578 to SATA Datasheet]

Enclosure information:
* [https://files.pine64.org/doc/datasheet/case/ROCK64%20Aluminum%20Waterproof%20Die%20Cast%20Casing.pdf Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]

Remote control button mapping:
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Enclosures ==

[[File:Rock64-Al-Case1-1.jpg|thumb|100px]]

The ROCK64 fits in three officially sold cases.

* [["Model B" Acrylic Open Enclosure]], [https://pine64.com/product/model-b-acrylic-open-enclosure/ Store]
* "Model B" Aluminum Waterproof Enclosure, [https://pine64.com/product/model-b-aluminum-waterproof-enclosure/ Store]
* [[ROCK64 Premium Aluminum Casing]], [https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66 Store]

== Troubleshooting ==

=== HDMI output disconnects as soon as it connects ===

Some older monitors seemingly can get into a weird state wherein the ROCK64 is unable to establish a proper connection with them. [[User:CounterPillow]] has seen this happen on an iiyama ProLite G2773HS connected over HDMI, and an Acer P225HQL connected over an HDMI to DVI adapter. The symptoms usually are that you see the monitor briefly turn on its backlight without displaying a picture, but then immediately either shutting off again or showing a "No Signal" message.

The solution is to completely power down your ROCK64, also removing its power source. Then plug in the monitor, and start up the ROCK64 afterwards. You should now be getting a picture again.

=== Power button doesn't do anything on a short press (Linux) ===

Make sure the <code>rk805_pwrkey</code> module is loaded, e.g. with <code>lsmod | grep rk805_pwrkey</code>. The module auto loading of <code>rk805_pwrkey</code> was fixed in the following upstream kernels: v6.0/v5.15.66/v5.10.142/v5.4.213/v4.19.258/v4.14.293 so there should be no requirement for fixes with those kernels or newer. If it doesn't show up, do a <code>modprobe rk805_pwrkey</code> as root. To make this persistent, create a <code>99-rk805_pwrkey.conf</code> in <code>/etc/modules-load.d/</code> with the content <code>rk805_pwrkey</code>

If it still doesn't work, make sure your init system is actually listening to the button press. With systemd, check <code>/etc/systemd/logind.conf</code> and make sure it's either all commented out (uses defaults) or contains something like <code>HandlePowerKey=poweroff</code>. You can change the short press action by setting <code>HandlePowerKey</code> to one of "ignore", "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", "hybrid-sleep", "suspend-then-hibernate", or "lock".

=== Video output is glitchy during activity ===

If your video output glitches out while there is memory bandwidth pressure, the likely reason is that the video output (VOP) quality-of-service (QoS) registers aren't set to high priority mode.

[[User:CounterPillow]] submitted [https://overviewer.org/~pillow/up/c5179dcb67/0001-rockchip-rk3328-Set-VOP-QoS-to-high-priority.patch a patch] to u-boot to fix this, but someone still needs to write a kernel patch to save/restore the QoS registers from the power domain driver.

== Other Resources ==
* [https://forum.pine64.org/forumdisplay.php?fid=85 ROCK64 Forum]
* IRC Server: irc.pine64.org Channel: ROCK64
* [https://github.com/rock64-linux ROCK64 Linux GitHub Repo]
* [https://github.com/ayufan-rock64 ROCK64 ayufan GitHub Repo]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://github.com/JamesLinEngineer/RKMC Rockchip Android RKMC (Forked from Kodi 16.1)]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* [https://www.armbian.com/rock64 Armbian's ROCK64 Page]

[[Category:ROCK64]] [[Category:Rockchip RK3328]]

PineNote

2024-11-17T22:41:40Z

Dsimic: /* System Memory */ Ditto

[[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.}}

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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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
* 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-11-17T22:41:15Z

Dsimic: /* Core */ Fits better

[[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.}}

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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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
* 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 Memory : 4 GB LPDDR4
* Flash Memory: 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-17T22:36:51Z

Dsimic: /* System Memory */ Ditto

[[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.}}

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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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: 4 GB LPDDR4
* Storage: 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 Memory : 4 GB LPDDR4
* Flash Memory: 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-17T22:36:17Z

Dsimic: /* Core */ Cleaned up a bit and clarified

[[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.}}

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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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: 4 GB LPDDR4
* Storage: 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 Memory : 4GB LPDDR4.
* Flash Memory: 128GB eMMC

== 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]]

ROCKPro64

2024-11-17T07:30:50Z

Dsimic: /* No Video or GPU Acceleration on Debian */ Should fit here better

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful single-board computer released by PINE64. It is powered by a Rockchip RK3399 hexa-core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-bit processor with a Mali T-860 quad-core GPU. The key features include a PCI Express (PCIe) x4 open-ended slot, the use of LPDDR4 DRAM, and industry-standard heatsink mounting holes.

The ROCKPro64 is equipped with 2 or 4 GB of LPDDR4 system memory, and 128 Mb of SPI boot flash. There is also an optional eMMC module (up to 128 GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 Type-C host port with DP 1.2, 1x USB 3.0 Type-A host port, 2x USB 2.0 host port, Gigabit Ethernet, PI-2 GPIO bus, MiPi DSI interface, eDP interface, touch panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different operating systems (OSes) are freely available from the open-source community, such as Linux (Ubuntu, Debian, Arch), BSD and Android.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector (Note: Some datasheets indicate a low supported number of mating cycles.)
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===

* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, supports SDHC and SDXC
* eMMC - bootable (optional eMMC module)
* 1x USB 3.0 host port
* 1x USB Type-C OTG port with alternate mode DP output
* 2x USB 2.0 dedicated host port

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO header
* PCI Express 2.1 x4 (four full-duplex lanes) open-ended port, [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 limited] to the Gen1 speed

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7-inch LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. On Manjaro ARM (kernel 6.2.5), WIFI seems to be stable with the firmware file. On a 5GHz network (802.11AC), it is possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is nearly impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| [https://pine64.com/?product=rockpro64-playbox-enclosure ROCKPro64 Playbox Enclosure]
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/product/rockpro64-30mm-tall-profile-heatsink/ ROCKPro64 30 mm Tall-Profile Heatsink]
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| [https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink Fan For ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCI Express 2.1
|
|
|
|
|
| The PCI Express interface of the RK3399 [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 is limited] to the Gen1 speed. As a result, some installed PCI Express devices may operate with degraded performance, such as M.2 SSDs that support fewer than four PCI Express lanes, installed using an adapter like [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card/ this one].
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| [https://pine64.com/product/rtc-backup-battery-holder-cr-2032/ RTC Backup Battery Holder CR2032]
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board dimensions: 133 mm x 80 mm x 19 mm
* Power input: 12 V, 3 A or 5 A, using 5.5 mm (OD) / 2.1 mm (ID) type M barrel DC connector (also known as DC 5521)
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [[:File:Pine64-rockpro64-component-placement-top-v21-20180702.pdf|ROCKPro64 v2.1 Board Top Silkscreen in PDF format]] (contains component labels)
** [[:File:Pine64-rockpro64-component-placement-bottom-v21-20180702.pdf|ROCKPro64 v2.1 Board Bottom Silkscreen in PDF format]] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://files.pine64.org/doc/rockpro64/Rockpro64-ver2.0-topsilk_ref.pdf ROCKPro64 v2.0 Board Top Silkscreen in PDF format] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

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

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]
* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]
* [[ROCKPro64 Device Tree Overlays on Mainline]]
* [[ROCKPro64 Hardware Tweaks]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NAS Case|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A [[Quartz64]] Model-A mounted in an ITX case using 3D printed brackets, which can also be used for the ROCKPro64]]

Allows mounting a ROCKPro64 or Quartz64 Model-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

'''Note:''' This issue should be non-existent in newer versions of the Linux kernel, as well as in long-term support (LTS) kernels, with [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80f4e62730a91572b7fdc657f7bb747e107ae308 this upstream kernel commit] that introduced the required module dependency.

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in the kernel log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

To fix this issue, run the following as <code>root</code> and reboot:

echo governor_simpleondemand >> /etc/initramfs-tools/modules
update-initramfs -u -k $(uname -r)

=== PCIe probe failures on Linux kernel boot ===

While booting the Linux kernel, you might experience PCIe probe failures, which render the attached PCIe device inaccessible. The [https://lore.kernel.org/all/20230509153912.515218-1-vincenzopalazzodev@gmail.com/ "drivers: pci: introduce configurable delay for Rockchip PCIe bus scan"] thread on the Linux kernel mailing list (LKML) discusses this issue and proposes a fix.

Manjaro ARM applies the following patches to the kernel package, which fix the issue:

* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch 1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch]
* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch 1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch]

[[Category:ROCKPro64]]
[[Category:Rockchip RK3399]]

ROCKPro64

2024-11-17T07:29:20Z

Dsimic: /* No Video or GPU Acceleration on Debian */ Expanded a bit, to mention the upstream fix

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful single-board computer released by PINE64. It is powered by a Rockchip RK3399 hexa-core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-bit processor with a Mali T-860 quad-core GPU. The key features include a PCI Express (PCIe) x4 open-ended slot, the use of LPDDR4 DRAM, and industry-standard heatsink mounting holes.

The ROCKPro64 is equipped with 2 or 4 GB of LPDDR4 system memory, and 128 Mb of SPI boot flash. There is also an optional eMMC module (up to 128 GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 Type-C host port with DP 1.2, 1x USB 3.0 Type-A host port, 2x USB 2.0 host port, Gigabit Ethernet, PI-2 GPIO bus, MiPi DSI interface, eDP interface, touch panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different operating systems (OSes) are freely available from the open-source community, such as Linux (Ubuntu, Debian, Arch), BSD and Android.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector (Note: Some datasheets indicate a low supported number of mating cycles.)
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===

* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, supports SDHC and SDXC
* eMMC - bootable (optional eMMC module)
* 1x USB 3.0 host port
* 1x USB Type-C OTG port with alternate mode DP output
* 2x USB 2.0 dedicated host port

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO header
* PCI Express 2.1 x4 (four full-duplex lanes) open-ended port, [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 limited] to the Gen1 speed

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7-inch LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. On Manjaro ARM (kernel 6.2.5), WIFI seems to be stable with the firmware file. On a 5GHz network (802.11AC), it is possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is nearly impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| [https://pine64.com/?product=rockpro64-playbox-enclosure ROCKPro64 Playbox Enclosure]
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/product/rockpro64-30mm-tall-profile-heatsink/ ROCKPro64 30 mm Tall-Profile Heatsink]
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| [https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink Fan For ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCI Express 2.1
|
|
|
|
|
| The PCI Express interface of the RK3399 [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 is limited] to the Gen1 speed. As a result, some installed PCI Express devices may operate with degraded performance, such as M.2 SSDs that support fewer than four PCI Express lanes, installed using an adapter like [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card/ this one].
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| [https://pine64.com/product/rtc-backup-battery-holder-cr-2032/ RTC Backup Battery Holder CR2032]
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board dimensions: 133 mm x 80 mm x 19 mm
* Power input: 12 V, 3 A or 5 A, using 5.5 mm (OD) / 2.1 mm (ID) type M barrel DC connector (also known as DC 5521)
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [[:File:Pine64-rockpro64-component-placement-top-v21-20180702.pdf|ROCKPro64 v2.1 Board Top Silkscreen in PDF format]] (contains component labels)
** [[:File:Pine64-rockpro64-component-placement-bottom-v21-20180702.pdf|ROCKPro64 v2.1 Board Bottom Silkscreen in PDF format]] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://files.pine64.org/doc/rockpro64/Rockpro64-ver2.0-topsilk_ref.pdf ROCKPro64 v2.0 Board Top Silkscreen in PDF format] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

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

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]
* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]
* [[ROCKPro64 Device Tree Overlays on Mainline]]
* [[ROCKPro64 Hardware Tweaks]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NAS Case|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A [[Quartz64]] Model-A mounted in an ITX case using 3D printed brackets, which can also be used for the ROCKPro64]]

Allows mounting a ROCKPro64 or Quartz64 Model-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in the kernel log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

To fix this issue, run the following as <code>root</code> and reboot:

echo governor_simpleondemand >> /etc/initramfs-tools/modules
update-initramfs -u -k $(uname -r)

'''Note:''' This issue should be non-existent in newer versions of the Linux kernel, as well as in long-term support (LTS) kernels, with [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80f4e62730a91572b7fdc657f7bb747e107ae308 this upstream kernel commit] that introduced the required module dependency.

=== PCIe probe failures on Linux kernel boot ===

While booting the Linux kernel, you might experience PCIe probe failures, which render the attached PCIe device inaccessible. The [https://lore.kernel.org/all/20230509153912.515218-1-vincenzopalazzodev@gmail.com/ "drivers: pci: introduce configurable delay for Rockchip PCIe bus scan"] thread on the Linux kernel mailing list (LKML) discusses this issue and proposes a fix.

Manjaro ARM applies the following patches to the kernel package, which fix the issue:

* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch 1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch]
* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch 1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch]

[[Category:ROCKPro64]]
[[Category:Rockchip RK3399]]

ROCKPro64

2024-11-17T07:22:12Z

Dsimic: /* 3D printable ITX mounting brackets */ Ditto

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful single-board computer released by PINE64. It is powered by a Rockchip RK3399 hexa-core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-bit processor with a Mali T-860 quad-core GPU. The key features include a PCI Express (PCIe) x4 open-ended slot, the use of LPDDR4 DRAM, and industry-standard heatsink mounting holes.

The ROCKPro64 is equipped with 2 or 4 GB of LPDDR4 system memory, and 128 Mb of SPI boot flash. There is also an optional eMMC module (up to 128 GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 Type-C host port with DP 1.2, 1x USB 3.0 Type-A host port, 2x USB 2.0 host port, Gigabit Ethernet, PI-2 GPIO bus, MiPi DSI interface, eDP interface, touch panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different operating systems (OSes) are freely available from the open-source community, such as Linux (Ubuntu, Debian, Arch), BSD and Android.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector (Note: Some datasheets indicate a low supported number of mating cycles.)
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===

* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, supports SDHC and SDXC
* eMMC - bootable (optional eMMC module)
* 1x USB 3.0 host port
* 1x USB Type-C OTG port with alternate mode DP output
* 2x USB 2.0 dedicated host port

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO header
* PCI Express 2.1 x4 (four full-duplex lanes) open-ended port, [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 limited] to the Gen1 speed

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7-inch LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. On Manjaro ARM (kernel 6.2.5), WIFI seems to be stable with the firmware file. On a 5GHz network (802.11AC), it is possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is nearly impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| [https://pine64.com/?product=rockpro64-playbox-enclosure ROCKPro64 Playbox Enclosure]
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/product/rockpro64-30mm-tall-profile-heatsink/ ROCKPro64 30 mm Tall-Profile Heatsink]
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| [https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink Fan For ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCI Express 2.1
|
|
|
|
|
| The PCI Express interface of the RK3399 [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 is limited] to the Gen1 speed. As a result, some installed PCI Express devices may operate with degraded performance, such as M.2 SSDs that support fewer than four PCI Express lanes, installed using an adapter like [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card/ this one].
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| [https://pine64.com/product/rtc-backup-battery-holder-cr-2032/ RTC Backup Battery Holder CR2032]
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board dimensions: 133 mm x 80 mm x 19 mm
* Power input: 12 V, 3 A or 5 A, using 5.5 mm (OD) / 2.1 mm (ID) type M barrel DC connector (also known as DC 5521)
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [[:File:Pine64-rockpro64-component-placement-top-v21-20180702.pdf|ROCKPro64 v2.1 Board Top Silkscreen in PDF format]] (contains component labels)
** [[:File:Pine64-rockpro64-component-placement-bottom-v21-20180702.pdf|ROCKPro64 v2.1 Board Bottom Silkscreen in PDF format]] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://files.pine64.org/doc/rockpro64/Rockpro64-ver2.0-topsilk_ref.pdf ROCKPro64 v2.0 Board Top Silkscreen in PDF format] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

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

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]
* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]
* [[ROCKPro64 Device Tree Overlays on Mainline]]
* [[ROCKPro64 Hardware Tweaks]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NAS Case|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A [[Quartz64]] Model-A mounted in an ITX case using 3D printed brackets, which can also be used for the ROCKPro64]]

Allows mounting a ROCKPro64 or Quartz64 Model-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in the kernel log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

To fix this issue, run the following as <code>root</code> and reboot:

echo governor_simpleondemand >> /etc/initramfs-tools/modules
update-initramfs -u -k $(uname -r)

=== PCIe probe failures on Linux kernel boot ===

While booting the Linux kernel, you might experience PCIe probe failures, which render the attached PCIe device inaccessible. The [https://lore.kernel.org/all/20230509153912.515218-1-vincenzopalazzodev@gmail.com/ "drivers: pci: introduce configurable delay for Rockchip PCIe bus scan"] thread on the Linux kernel mailing list (LKML) discusses this issue and proposes a fix.

Manjaro ARM applies the following patches to the kernel package, which fix the issue:

* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch 1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch]
* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch 1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch]

[[Category:ROCKPro64]]
[[Category:Rockchip RK3399]]

ROCKPro64

2024-11-17T07:21:45Z

Dsimic: /* 3D printable ITX mounting brackets */ Clarified a bit

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful single-board computer released by PINE64. It is powered by a Rockchip RK3399 hexa-core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-bit processor with a Mali T-860 quad-core GPU. The key features include a PCI Express (PCIe) x4 open-ended slot, the use of LPDDR4 DRAM, and industry-standard heatsink mounting holes.

The ROCKPro64 is equipped with 2 or 4 GB of LPDDR4 system memory, and 128 Mb of SPI boot flash. There is also an optional eMMC module (up to 128 GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 Type-C host port with DP 1.2, 1x USB 3.0 Type-A host port, 2x USB 2.0 host port, Gigabit Ethernet, PI-2 GPIO bus, MiPi DSI interface, eDP interface, touch panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different operating systems (OSes) are freely available from the open-source community, such as Linux (Ubuntu, Debian, Arch), BSD and Android.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector (Note: Some datasheets indicate a low supported number of mating cycles.)
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

=== Audio ===

* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, supports SDHC and SDXC
* eMMC - bootable (optional eMMC module)
* 1x USB 3.0 host port
* 1x USB Type-C OTG port with alternate mode DP output
* 2x USB 2.0 dedicated host port

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO header
* PCI Express 2.1 x4 (four full-duplex lanes) open-ended port, [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 limited] to the Gen1 speed

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7-inch LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. On Manjaro ARM (kernel 6.2.5), WIFI seems to be stable with the firmware file. On a 5GHz network (802.11AC), it is possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is nearly impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| [https://pine64.com/?product=rockpro64-playbox-enclosure ROCKPro64 Playbox Enclosure]
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/product/rockpro64-30mm-tall-profile-heatsink/ ROCKPro64 30 mm Tall-Profile Heatsink]
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| [https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| [https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink Fan For ROCKPro64 20 mm Mid-Profile Heatsink]
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCI Express 2.1
|
|
|
|
|
| The PCI Express interface of the RK3399 [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=712fa1777207 is limited] to the Gen1 speed. As a result, some installed PCI Express devices may operate with degraded performance, such as M.2 SSDs that support fewer than four PCI Express lanes, installed using an adapter like [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card/ this one].
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| [https://pine64.com/product/rtc-backup-battery-holder-cr-2032/ RTC Backup Battery Holder CR2032]
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board dimensions: 133 mm x 80 mm x 19 mm
* Power input: 12 V, 3 A or 5 A, using 5.5 mm (OD) / 2.1 mm (ID) type M barrel DC connector (also known as DC 5521)
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [[:File:Pine64-rockpro64-component-placement-top-v21-20180702.pdf|ROCKPro64 v2.1 Board Top Silkscreen in PDF format]] (contains component labels)
** [[:File:Pine64-rockpro64-component-placement-bottom-v21-20180702.pdf|ROCKPro64 v2.1 Board Bottom Silkscreen in PDF format]] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://files.pine64.org/doc/rockpro64/Rockpro64-ver2.0-topsilk_ref.pdf ROCKPro64 v2.0 Board Top Silkscreen in PDF format] (contains component labels)
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

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

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]
* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]
* [[ROCKPro64 Device Tree Overlays on Mainline]]
* [[ROCKPro64 Hardware Tweaks]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NAS Case|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A [[Quartz64]] Model-A mounted in an ITX case using 3D printed brackets, which can also be used for the ROCKPro64]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in the kernel log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

To fix this issue, run the following as <code>root</code> and reboot:

echo governor_simpleondemand >> /etc/initramfs-tools/modules
update-initramfs -u -k $(uname -r)

=== PCIe probe failures on Linux kernel boot ===

While booting the Linux kernel, you might experience PCIe probe failures, which render the attached PCIe device inaccessible. The [https://lore.kernel.org/all/20230509153912.515218-1-vincenzopalazzodev@gmail.com/ "drivers: pci: introduce configurable delay for Rockchip PCIe bus scan"] thread on the Linux kernel mailing list (LKML) discusses this issue and proposes a fix.

Manjaro ARM applies the following patches to the kernel package, which fix the issue:

* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch 1005-rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch]
* [https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/44e81d83b7e002e9955ac3c54e276218dc9ac76d/1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch 1007-arm64-dts-rockchip-Add-PCIe-bus-scan-delay-to-RockPr.patch]

[[Category:ROCKPro64]]
[[Category:Rockchip RK3399]]

Pinecil: Test, Repair, Issues

2024-11-16T20:23:04Z

Dsimic: /* Assemble steps */ Fixed a typo

This article explains some common issues and fixes which includes how to dismantle, test and do some repairs.

== Cautions ==

{{warning| while opening your Pinecil will not necessarily void your warranty, all self-repairs are '''done at your own risk'''. Read everything in this section and related or linked articles to get a good idea of the procedure, and go to the Pinecil community chat if you desire advice/support from experienced volunteers. Self-repairs or modifications might void your warranty so proceed if this is not a concern. This information is for educational purposes only.}}

Pinecil V1 and V2 have slightly different schematics and have different MCU chips. Doing repairs often requires referencing the correct schematics or photos. The datasheets are also important to get information about the chips, and to order replacement parts. The schematics and known datasheets are all at the bottom of this article and linked in the contents table at the top. Chatting with other owners of Pinecil is encouraged as they have experience - already broke things so you don't have to (see Pinecil volunteer [[Pinecil#Live_Community_Chat |chat link here]]).

{{Info|This is a new work in progress (WIP) started Feb. 18, 2023 which may be updated over time as volunteers have time to write up information. For sections that are missing, try asking in the live chat as a volunteer may have some clues to get you headed in the right path.}}

== Tools needed ==

# Digital multimeter (DMM)
# Philips screwdriver
# All schematics, datasheets for known common parts, and links to where to buy replacement parts are all in this article under [[#Schematics_and_Board_Data| Schematics and board data]].
#* Refer to the correct section for V1 or V2 parts.
#* Which model do I have? The older V1 model has an all black handle with a blue silicone grip and was discontinued in July 2022. The new V2 model has a black handle with a green thumb grip and is the only model PINE64 and authorized resellers started selling after August 1, 2022.
# Magnifying lamp or jeweler's glasses with led light and good room light.
# Photos/videos will help to chat with volunteers in the [[Pinecil#Live_Community_Chat|live Pinecil chat channel]] if getting clarification or troubleshooting.
# Optional: mobile phone to take macro photos or video. A macro lens to take phone photos is helpful; there are cheap ones that simply clip on.
# Possibly another soldering iron to do the repair, some flux, solder, and isopropyl alcohol (IPA) for cleaning the PCB. See [[Pinecil_Cases,_Stands,_Supplies#Soldering_supplies| this guide]] for some basic supply options.
# Optional: better needle size probe leads for DMM makes things easier and are nice for electronic work.
# Reference photos are in the [[#Images| Images section below]].

== Dismantle steps ==

=== Easy trick to open Pinecil ===

* Video of easy trick: https://www.youtube.com/watch?v=aK01V5DrrVk

* Handle replacement [https://wiki.pine64.org/wiki/File:Pinecil_Shell_Replacement_Guide.pdf graphic]

* Step-by-step

# It is recommended to take photos to help with reassembly.
# Loosen the top tip screw (PH1) (top is the side with the screen).
# Gently pull the tip out and set aside (let the tip cool down first or use protection to prevent burns).
# Slide the rubber thumb grip off the front.
# Remove the bottom-front screw (between the bottom feet (PH1)).
# Remove the ground screw (longer m2x4mm screw next to the screen near the (-) button (PH1)).
# Slightly pull the two halves of the case apart at the tip front end first, enough to get a fingernail or guitar pick between 2 parts.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by sliding it a little forward (it is retained by the top half at the DC barrel side).
# Remove the screws retaining the copper tip contacts (PH000, M1.4 x 5).
# Remove the copper tip contacts (note the orientation of the contacts & tiny tab hole).
# Lift the PCB gently up from Tip end.
# Remove the round copper ring contact from under the PCB, near the tip end of the handle (this is installed first before the PCB because it provides ground contact from the front of the Pinecil to the rear ground screw).
# Remove the two small round buttons so they do not get lost.

== Assemble steps ==

# Place the two round buttons into the two holes in the top half of the case.
# Install the round copper ground ring at the tip end '''before installing the PCB'''.
# Place the PCB board into handle at an angle, DC barrel end goes in first.
## Lower the rest of the board into the case and align the PCB with the two contact screw holes.
# Install the two copper tip contacts (note the small tab on the contact and the small hole in the PCB for it).
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align. Also make sure that the protective baffle in the top half of the case, which keeps the copper ground ring in its place, aligns properly with the ring itself.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.

{{Info|For normal operation of the iron, omission of the copper ring in step #2 does not impact operation. If you are working with ESD components, you need it in order to ground the iron tip via the earth screw at the back of the iron. It is recommended to keep this installed.}}

{{Warning|Make sure that the copper ground ring in step #2 is installed so it sits flush with the grounding metal insert in the bottom half of the case. Failure to do so may cause the copper ground ring touch one of the copper tip contacts in step #6, which may later cause damage to some of the components on the PCB.}}

== FAQ ==

=== Common Fixes ===

# Sometimes, just updating to the newest firmware fixes issues as Ralim and team are very active in adding features and <s>bug fixes</s> enhancements (see [[Pinecil#Firmware_&_Updates| Firmware]]).
# Some [https://ralim.github.io/IronOS/Troubleshooting/ Troubleshooting information] is also on GitHub Ralim's IronOS (which is the firmware that is on the Pinecil). There are several hidden Debug tools in the firmware that also help with diagnosis.
# Clean all new Tips (Cartridges) with 90%-99% IPA (Isopropyl Alcohol) especially the white end with the 2 silver contacts.
# If you can't find the information here or it hasn't been written yet; simply join the volunteer run [[Pinecil#Live_Community_Chat| live Pinecil chat channel]]. Sometimes you can get a clue to the right path.

=== Common Questions ===

# '''Temperature is flickering wildly''':
#* Most likely just need to clean whole cartridge/tip with IPA ([https://github.com/Ralim/IronOS/issues/1601 reference issue]). See [[#Poor_Contact_Fix|Poor Contact Fix here]].
#* If it's jumping wildly after reaching set temperature, this is also caused by using a low amp/volt charger that is below the 3amp minimum required for pinecil (per manufacturer rating), upgrading to a 3.25amp/20V USB-C charger often fixes this ([https://github.com/Ralim/IronOS/issues/1644 reference issue]).
#* Some people might see a random spike while idle. Solution: update firmware, there are some ADC timing adjustments in IronOS 2.21+; it's a good idea to keep your firmware updated to newest stable release ([https://github.com/Ralim/IronOS/issues/1485 reference issue]). This fix is included in 2.21+ release.
# '''Screen shows X symbol''' (no tip installed) and I have a tip installed. Ensure the cartridge/tip is properly installed: remove the front Tip screw, check that the cartridge/tip is pushed all the way in and the round metal collar is pressed against the black handle [https://wiki.pine64.org/wiki/File:Pinecilv2-1.jpg see photo here]. Reinstall the screw. See [[#Tip_Problems|Tip Problems]] and [[#Poor_Contact_repair|Poor Contact repair]].
# '''Screen shows the symbol (X) randomly on new Pinecil''': tip is installed and it heats up and works fine, but randomly I see the no tip symbol (X) come and go for a second. See #1 above, it is most likely the same reason, clean the metal contacts on the rear of the cartridge/tip (even if it looks clean, could have residue/oils). Follow the same instructions for [[#Poor_Contact_Fix|Poor Contact Fix here]]. [https://github.com/Ralim/IronOS/issues/1601 Reference ticket on Github].
# '''How do I install the optional Hall Effect Sensor?''' See the [[Pinecil_Hall_Effect_Sensor| Hall Effect Sensor]] article for installation; location is U14 on the PCB & in the Schematics. Reference schematics section [[#Schematics_and_Board_Data| here]] also.
# '''Help, I think I bricked Pinecil doing an update''': no worries, it's very hard to brick a Pinecil because of the way the firmware is loaded in ROM. Usually just flashing again with a newer or different version brings it back to life ([[Pinecil#Firmware_&_Updates|see Firmware]]). This can be done even if you can't see your screen anymore.
# '''My Pinecil keeps rebooting''': some laptop ports are not compatible to do updates and show pinecil screen rebooting, change to a different ports on the laptop or different machine (e.g., sometimes the USB-A port works where the usb-C did not). If it is rebooting connected to a power charger, change to a different charger or add a ground wire to your Pinecil ground screw (search for ''ts100 ground wire'' on a search engine). Also see the [[Pinecil#Power_Supplies_and_Watts|Power Supplies article]]. This could happen because of the way 2-prong no-ground chargers are made with no ground path for small current leakage. Also try to plug the charger into a surge protector strip (type that have 3-prong ground and plug the surge protector into a 3-prong grounded wall outlet). Try a different cable or flipping the cable over also.
# '''Tip is glowing red hot'''. Unplug immediately, you have most likely a blown MOSFET, check that out, replacement parts in Datasheets below. Tip is probably damaged too. Make sure you are using the correct rated charger for Pinecil (some cheap, universal or no-brand DC bricks can damage electronics from spiking voltages).
# '''My temperature display is way off and Pinecil is at room temerature''': first, check [[#Poor_Contact_Fix| poor contact fix here]]. Then enter the hidden debug menu and look for HAN C which is the internal handle temperature. This should normally be close to or slightly higher than the room temperature if the pinecil tip is also at room temperature. Under load, the HAN C can go up a bit, otherwise when the tip is cold, the HAN C should be close to ambient. Depending on your version of IronOS, the debug menu will show as HAN C or C Han. See IronOS [https://ralim.github.io/IronOS/Troubleshooting/ Troubleshooting here], especially about CHan and the Temperature sensor. If the reading is out of spec (very low/high), and reflowing/resoldering the Temperature sensor does not work, replacement might be needed.
# '''I see <code>Thermal Runaway</code> or <code>Undervoltage</code> messages on the screen'''. This is often caused by using a weak power supply that does not have a minimum of 12V-3amps and is not rated to work with Pinecil. Pinecil will stop heat to the tip and display <code>Thermal Runaway</code>.
#* TL;DR get a USB-C charger 20V 3.25 amps, PD 65W (best bang for the buck for good Pinecil performance) many available between $15-$25.
#* Detailed information on chargers and suggested types is in the article [[Pinecil Power Supplies]].
# '''I plugged in the wrong kind of DC barrel charger, it was a not Center-positive pin and now the Pinecil won't turn on''': see [[#Reverse_polarity_damage| Reverse polarity damage]]. Usually requires replacing the MOSFET (U13) and Buck Converter/Step-down (U8). See the datasheets for links to parts.
# '''I hear a sizzling/crackle sound from my new Pinecil''': this small noise is usually fine and may disappear after a few days of use, see [[#Hissing_Crackle_Sound| Hissing Crackle Sound]].
# '''Screen is black''': first try to update firmware. Check out the IronOS troubleshooting [https://ralim.github.io/IronOS/Troubleshooting/#no-display-or-dots-on-the-display guide here] for possible issues. See the [[#Datasheets_for_Components|datasheets here]] at the bottom of this article for links to replacement parts. Repair method would be similar to ts100 screens of which there are many guides like [https://www.youtube.com/watch?v=HlWAY0oYPFI this video]. If the tip heats up, but screen is black, the OLED may have failed/burned out. If tip does not heat up, it may be something else. Sometimes just reflow/reheat the solder for the OLED screen fixes issues. Using OLED screen at lower brightness extends the life.

== Solutions ==

=== Hissing Crackle Sound ===

# The sizzle sound will usually go away after a few days of use and heating up the iron. First, clean the tip contacts (at the white end of the cartridge) with IPA (isopropyl alcohol), heat it up a few times to 350 °C to break it in (add solder to the tip to protect it).
# Ralim said, "there is usually a bit of noise when you first use it, and a slight hiss/pop noise from the handle and that is normal. depends a bit on exactly what batch of caps are in your unit. The Tip drive signal is AC coupled through a capacitor for safety, downside is that it means the firmware is hitting that cap with a square wave the whole time the tip is on. Once you have heated up the duty cycle, it drops off so it's not as noticeable."
# Some members reported that after they opened their new Pinecil, wiped the PCB and tips gently with IPA, let it dry, all the sizzling noise went away. They also did a break-in of the new tips, bringing the temperature to 350 C a few times.
# Video of similar [https://www.reddit.com/r/soldering/comments/qv66a6/weird_crackling_noise_from_ts100_not_from_the_hot/ crackle sound] on the ts100 iron (don't have example of Pinecil, but it's similar sound).

=== Cartridge/Tip Problems ===

# Wipe entire tip (cartridge) clean, details in [[#Poor_Contact_test_and_repair|Poor Contact]] section
# Using a multimeter, switch it to ohms to measure resistance. Measure the two silver bands at the rear (white end).
# If it measures OL or infinity, or extremely out of the spec range below, it might be bad.
# Note, only measure when cartridge/tip is cold and unused for a couple hours (a warm tip will have much higher resistance/ohm reading).
#* Normal ts100 style tips should measure ~7.8 ohms - 8.3 ohms (when cold)
#* PINE64 brand Short tips should measure ~6.1-6.5 ohms (when cold).
#* See the [[Pinecil Tips]] for more details.

=== Poor Contact Fix ===

[[File:CleanTip-Cartridge-Contacts.jpg|none|300px|thumb| Clean contacts with IPA]]

# Most likely the tip (cartridge) is not making good contact (at the silver bands on the rear white end). Usually this issue goes away after a few days of use as the cartridge rubs against the internal contacts more. New cartridges could have factory residue or oils on them that interferes with the R-tip reading.
# To fix this issue quicker, wipe all new tips (cartridges) with a dry towel or 90-99% IPA (isopropyl alcohol) especially the two silver contacts at the white end (do not use water to wipe as it could get into the seam line on the white end).
# With the Pinecil unplugged, remove and reinsert the tip a couple times and spin it a little inside against the contacts. Then plug it in and heat it up to 350 °C a few times for a couple minutes. These steps tend to resolve most new Pinecil or new cartridges causing flickering temperatures or "no-tip" icon displays randomly.
# Always unplug Pinecil before swapping tips. Hot swapping is not a good idea, and for the V2 this could cause strange behavior as the V2 auto-detects tip resistance only on power-up or reboot.
# Sometimes just disassembling and reassembling all parts back correctly and installing the 2 internal contacts with screws correctly also helps.
# Poor contact could happen if the tips are not clean or brand new with factory residue or not making good contact with the internal clips inside the Pinecil. The two contacts inside might need to also be removed, wiped and reinstalled with the two screws (ensure the small metal tab on the clip sits into the small hole in the PCB).
# See '''[[Pinecil_Tips#How_to_check_new_tips?| Pinecil Tips]]''' article for more details on testing.

=== Not Powering Up Anymore ===

There are reports
([https://forum.pine64.org/showthread.php?tid=12661 #1],
[https://www.reddit.com/r/PINE64official/comments/q8d08a/pinecil_does_not_power_on/ #2])
that Pinecil that has been working stopped powering on. Note this is different from black screen issue mentioned above - in this case, Pinecil simply does not power on and also does not recognized as an USB device. Also, it is not an USB-PD compatibility issue as the device has been working fine up until this issue.

It has been reported that dead USB-PD controller (FUSB302MPX) was the cause. While the root cause of the failure is still unknown, Pinecil can be 'repaired' by removing the chip, allowing it to be used as a DC-powered soldering iron. Removing FUSB302MPX (small 5x5mm QFN) requires some effort, but it is doable by careful desoldering (or hotair desoldering).

=== Reverse Polarity Damage ===

Pinecil requires a center-positive DC power supply which most are, but some are reverse polarity and will destroy the electronics if used. If you plugged in a "center-negative" DC power supply, most likely the MOSFET and the buck converter are broken. This usually requires replacing the MOSFET (U13) and buck converter / step-down (U8). See the datasheets for links to replacement parts which is at the bottom of this article [[#Datasheets_for_Components| here]].

{{Note|1='''Check the polarity''' of the DC barrel plug before plugging in a random charger. Incorrect polarity will break the Pinecil. The [https://www.youtube.com/watch?v=5DBTNplNTfA video here] shows how to check.}}

[[File:AC adaptor polarity.png|400px]]

[[File:Nintendo-center-negative.png|300px]]

Reference the article on [[Pinecil_Power_Supplies#DC_Barrel_Power| DC barrel chargers here]], (i.e., laptop bricks) for appropriate USB-C and DC chargers that will work with the Pinecil.

== Images ==

<gallery mode="packed">
Image:PCP-Top-side-screen.jpg|Screen side: V2 on top, V1 below
Image:PCP-Bottom-Side.jpg|Pinecone side: V2 on top, V1 below
File:Pinecil v2 MOSFET.JPG | MOSFET V2 |alt=alt language
File:FUSB302-V2-02.JPG | FUSB302 V2 |alt=alt language
File:Pinecil LDOandOP-Amp.png| LDO and OP-Amp|alt=alt language
File:Under OLED screen01.png| Under the OLED screen, V2|alt=alt language
</gallery>

== Schematics and Board Data ==

=== Pinecil V2 mainboard schematic ===

* [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v2.0_20220608.pdf Pinecil mainboard schematic ver 2.0 20220608, this is production version schematic]
* [https://files.pine64.org/doc/Pinecil/Pinecil_PCB_placement_v2.0_20220608.pdf Pinecil mainboard ver 2.0 PCB Component Placement PDF file]

=== Pinecil V1 mainboard schematic ===

V1 was only sold until July 2022, and then discontinued for newer V2 model

* [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

== Datasheets for Components ==

=== Pinecil V2 datasheets ===

* Power MOSFET Switch: [https://datasheet.lcsc.com/lcsc/2105241831_HUASHUO-HSM4313_C2828487.pdf HSM4313], location U13 (replacement [https://lcsc.com/product-detail/MOSFETs_HUASHUO-HSM4313_C2828487.html HSM4313])
* LDO Regulator: [https://datasheet.lcsc.com/lcsc/1912111437_LOWPOWER-LP3986-33B3F_C387689.pdf LP 3986-33], Ultra-low noise, location U5 (replacement [https://www.lcsc.com/product-detail/Linear-Voltage-Regulators-LDO_LOWPOWER-LP3986-33B3F_C387689.html LP 3986-33])
* Buck Converter: [https://datasheet.lcsc.com/lcsc/2108072230_TECH-PUBLIC-TP6841S6_C2844736.pdf TP6841S6 40V], Step-Down, location U8 (replacement [https://www.lcsc.com/product-detail/DC-DC-Converters_TECH-PUBLIC-TP6841S6-A_C2844924.html TP6841S6-A])
* USB-C PD Controller: [https://rocelec.widen.net/view/pdf/0av2cqef3a/FAIR-S-A0001311862-1.pdf?t.download=true&u=5oefqw FUSB302MPX], location U1 (replacement [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-ICs_onsemi-Fusb302mpx_C442699.html FUSB302MPX])
* Acceleration/Gyroscope: [https://lcsc.com/product-detail/Attitude-Sensor-Gyroscope_Hangzhou-Silan-Microelectronics-SC7A20TR_C5126709.html SC7A20 sensor], Silan, location U9 (replacement unknown)
* NTC Temperature Sensor: [https://media.digikey.com/pdf/Data%20Sheets/TDK%20PDFs/NTCG163JF103FTDS_Spec.pdf NTCG163JF103FTDS], location NTC1 (replacement [https://lcsc.com/product-detail/span-style-background-color-ff0-NTC-span-Thermistors_TDK-NTCG163JF103FTDS_C435270.html NTC here]). Note that U10 is empty if NTC type thermistor is used.
* Optional Hall Effect Sensor: [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Si7210-B-00-IV(R)] by Silicon Labs, location U14. This is a user add-on and does not come installed on the PCB.
** [https://www.silabs.com/documents/public/application-notes/an1018-si72xx-sensors.pdf How magnets work near Hall Sensor Si7210]
** Replacement [https://lcsc.com/product-detail/Position-Sensor_SILICON-LABS-SI7210-B-00-IVR_C2654956.html Si7210-B-00-IV], also at Digikey and Mouser
* Operational Amplifier [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGM8557-1AXN5G], SGMicro, Low Noise OP Amp Datasheet, location U11 (replacement unknown).
* Display Screen OLED [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG-9616TSWCG02] datasheet (replacement [https://www.lcsc.com/product-detail/OLED-Displays-Modules_UG-Univision-Semicon-UG-9616TSWCG02_C88335.html QUG-9616TSWCG02] OLED Display).

MCU: Bouffalo Labs, BL-706_QFN48, RISC-V + 2.4 GHz RF SoC
* [https://lupyuen.github.io/articles/bl706 BL706 Analysis], by Lupyuen, includes datasheet, location U15.
* [https://dev.bouffalolab.com/media/doc/702/open/datasheet/en/html/index.html BL706 datasheet] and its [https://github.com/bouffalolab/bl_docs/blob/main/BL702_DS/en/BL702_704_706_DS_en_2.6.pdf PDF version]
* [https://dev.bouffalolab.com/media/doc/702/open/reference_manual/en/html/index.html BL706 Reference Manual] and its [https://github.com/bouffalolab/bl_docs/blob/main/BL702_RM/en/BL702_BL704_BL706_RM_en_1.2.pdf PDF version]
* [https://github.com/bouffalolab/bl_mcu_sdk SDK and Bouffalo documents]
* [https://datasheet.lcsc.com/lcsc/1912111437_TAE-Zhejiang-Abel-Elec-TAXM32M4ZFBCCT2T_C388797.pdf SMD Resonator] for Bluetooth BLE, 32MHZ/12PF-10PPM, SMD2016-4P, location UX1 (replacement [https://lcsc.com/product-detail/Crystals_TAE-Zhejiang-Abel-Elec-TAXM32M4ZFBCCT2T_C388797.html SMD Resonator]).

USB-C port:
* possible part, has not been verified: [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-Connectors_SHOU-HAN-TYPE-C-24P-QT_C2681555.html Replacement USB-C port]

=== Pinecil V1 datasheets ===

* Buck converter: [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf RT7272B 3A Datasheet], Ricktek, Step-Down converter, location U8
* LDO Regulator: [https://datasheet.lcsc.com/lcsc/1912111437_LOWPOWER-LP3986-33B3F_C387689.pdf LP 3986-33], location U5, ([https://www.lcsc.com/product-detail/Linear-Voltage-Regulators-LDO_LOWPOWER-LP3986-33B3F_C387689.html Replacement here]).
* MOSFET Switch: [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf CJQ7328 8A datasheet], Chang Jiang.
** Hint: people have replaced V1 mosfet using the better rated one from the newer V2 datasheets (HSM4313 has same footprint and higher rating), see V2 section for MOSFET.
* Acceleration [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Sensor Datasheet]
* Temperature Sensor: [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Datasheet], location U10, (possible [https://www.lcsc.com/product-detail/Temperature-Sensors_Analog-Devices-TMP36GRTZ-REEL7_C129489.html replacement here]).
* Optional Hall Effect Sensor: [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Si7210-B-00-IV(R) by Silicon Labs, location U14]. This is a user add-on and does not come installed on the pcb.
** ([https://www.silabs.com/documents/public/application-notes/an1018-si72xx-sensors.pdf How magnets work near Hall Sensor Si7210])
** ([https://lcsc.com/product-detail/Position-Sensor_SILICON-LABS-SI7210-B-00-IVR_C2654956.html One place to buy it], also at Digikey and Mouser)
* OLED Display screen: [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller: [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF FUSB302 USB PD Datasheet]
* OP Amp information: [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet (U11)]
* Capacitors: [https://lcsc.com/product-detail/Multilayer-Ceramic-Capacitors-MLCC-SMD-SMT_YAGEO-CC0603KRX7R9BB105_C559769.html possible replacement part for C5, 1uF/50V]
* USB-C port: possible part, has not been verified: [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-Connectors_SHOU-HAN-TYPE-C-24P-QT_C2681555.html Replacement]

GigaDevice RISC-V SoC data:

* [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
* [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]

Breakout Board Datasheet: [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LP6498B6F 1.2A Switching Power Regulator]

== Pinecil V1, 24V Mod ==

{{warning|Do this at your own risk, read everything in this section and related/linked articles, and go to the Pinecil community chat if you desire advice. An incorrect cut of the trace could render the Pinecil non-working.}}

[[File:Pinecil-V1andV2.png|350px|thumb|right| Pinecil V1 has blue rubber. Newer Pinecil V2 has green rubber & Bluetooth LE chip]]

# This modification is '''Not''' for the V2 (sold after Aug 1, 2022 with green thumb grip) as the V2 '''already''' has 24V DC barrel charger capability.
# If you have an older V1 model, then first upgrade to the newest [[Pinecil#Firmware_&_Updates|firmware here]] before starting this modification. The PD debug menu was added to the firmware in 2.17 and other important fixes came later. Access to the hidden PD debug menu is necessary to assist with this mod.
# See Ralim's IronOS for how to use the hidden [https://ralim.github.io/IronOS/DebugMenu/#pd-debug-menu PD Debug here] and check if your version of Pinecil V1 could benefit from the modification.
# If PD-Debug menu says "No VBUS", then stop here, you do not need the modification or any cut of the trace line, it will not benefit you because there is no connection to the VBUS already. If it says "w. Vbus" then continue. If you don't have a PD-Debug menu, then upgrade to the newest firmware first, see instructions above.
# Some models of V1 came with the PCB already capable of 24V as the Pine Store made modifications to the PCB (not all batches of V1 were the same). Do the PD debug test first to see if the mod is not required.
# See the February 2022 [https://www.pine64.org/2022/02/15/february-update-chat-with-the-machine/ Community update here]. The photo is incorrect in the article. It is ''not'' a before and after photo.
#* Photo shows two separate PCBs of Pinecil V1 made at different times; therefore, the trace is cut in a slightly different location depending on which one it looks like.
#* The PCB with 2 small via holes and is harder to cut in the correct location to avoid damaging the holes. This is called the "whalecil" in community chat (looks like a whale).

[[File:Pinecil V1 24V Mod.png|400px]]

PCB 1 style (left photo) is easier to cut the trace. Cut all the way across the trace and deep enough to cut the copper contact. PCB 2 style (right photo) is harder because the trace has to be cut without damaging the 2 via holes.

7. Don't plug in 24V until you first check with a USB-C PD charger that PD debug says '''No VBUS''' which means the mod is complete. If it still says '''W. Vbus''', then the connection still exist. Cut a little deeper and clean the cut with some IPA (isopropyl alcohol) to remove any copper dust, dry it and check again. Taking a macro photo with a phone helps to examine the cut.
If a USB-C charger is not available, often a phone with a USB-C port is a PD type, and can be used like a charger to plug in and check the PD debug messages (unfortunately, a PC port is not normally "PD" and won't give proper PD Debug).

8. If you want another set of eyes on it before you cut, post a photo of your PCB (near the Pinecone) on the Pine64 > [[Pinecil#Live_Community_Chat|live Pinecil chat channel]]. Ask for a volunteer who has ''completed'' the 24V mod on a Pinecil V1 to assist. Not all chat people own a Pinecil even if they are in the Pinecil channel.

[[Category:Pinecil]]

Pinecil: Test, Repair, Issues

2024-11-16T20:10:56Z

Dsimic: /* Assemble steps */ Described the protective baffle and its relation with the ground ring

This article explains some common issues and fixes which includes how to dismantle, test and do some repairs.

== Cautions ==

{{warning| while opening your Pinecil will not necessarily void your warranty, all self-repairs are '''done at your own risk'''. Read everything in this section and related or linked articles to get a good idea of the procedure, and go to the Pinecil community chat if you desire advice/support from experienced volunteers. Self-repairs or modifications might void your warranty so proceed if this is not a concern. This information is for educational purposes only.}}

Pinecil V1 and V2 have slightly different schematics and have different MCU chips. Doing repairs often requires referencing the correct schematics or photos. The datasheets are also important to get information about the chips, and to order replacement parts. The schematics and known datasheets are all at the bottom of this article and linked in the contents table at the top. Chatting with other owners of Pinecil is encouraged as they have experience - already broke things so you don't have to (see Pinecil volunteer [[Pinecil#Live_Community_Chat |chat link here]]).

{{Info|This is a new work in progress (WIP) started Feb. 18, 2023 which may be updated over time as volunteers have time to write up information. For sections that are missing, try asking in the live chat as a volunteer may have some clues to get you headed in the right path.}}

== Tools needed ==

# Digital multimeter (DMM)
# Philips screwdriver
# All schematics, datasheets for known common parts, and links to where to buy replacement parts are all in this article under [[#Schematics_and_Board_Data| Schematics and board data]].
#* Refer to the correct section for V1 or V2 parts.
#* Which model do I have? The older V1 model has an all black handle with a blue silicone grip and was discontinued in July 2022. The new V2 model has a black handle with a green thumb grip and is the only model PINE64 and authorized resellers started selling after August 1, 2022.
# Magnifying lamp or jeweler's glasses with led light and good room light.
# Photos/videos will help to chat with volunteers in the [[Pinecil#Live_Community_Chat|live Pinecil chat channel]] if getting clarification or troubleshooting.
# Optional: mobile phone to take macro photos or video. A macro lens to take phone photos is helpful; there are cheap ones that simply clip on.
# Possibly another soldering iron to do the repair, some flux, solder, and isopropyl alcohol (IPA) for cleaning the PCB. See [[Pinecil_Cases,_Stands,_Supplies#Soldering_supplies| this guide]] for some basic supply options.
# Optional: better needle size probe leads for DMM makes things easier and are nice for electronic work.
# Reference photos are in the [[#Images| Images section below]].

== Dismantle steps ==

=== Easy trick to open Pinecil ===

* Video of easy trick: https://www.youtube.com/watch?v=aK01V5DrrVk

* Handle replacement [https://wiki.pine64.org/wiki/File:Pinecil_Shell_Replacement_Guide.pdf graphic]

* Step-by-step

# It is recommended to take photos to help with reassembly.
# Loosen the top tip screw (PH1) (top is the side with the screen).
# Gently pull the tip out and set aside (let the tip cool down first or use protection to prevent burns).
# Slide the rubber thumb grip off the front.
# Remove the bottom-front screw (between the bottom feet (PH1)).
# Remove the ground screw (longer m2x4mm screw next to the screen near the (-) button (PH1)).
# Slightly pull the two halves of the case apart at the tip front end first, enough to get a fingernail or guitar pick between 2 parts.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by sliding it a little forward (it is retained by the top half at the DC barrel side).
# Remove the screws retaining the copper tip contacts (PH000, M1.4 x 5).
# Remove the copper tip contacts (note the orientation of the contacts & tiny tab hole).
# Lift the PCB gently up from Tip end.
# Remove the round copper ring contact from under the PCB, near the tip end of the handle (this is installed first before the PCB because it provides ground contact from the front of the Pinecil to the rear ground screw).
# Remove the two small round buttons so they do not get lost.

== Assemble steps ==

# Place the two round buttons into the two holes in the top half of the case.
# Install the round copper ground ring at the tip end '''before installing the PCB'''.
# Place the PCB board into handle at an angle, DC barrel end goes in first.
## Lower the rest of the board into the case and align the PCB with the two contact screw holes.
# Install the two copper tip contacts (note the small tab on the contact and the small hole in the PCB for it).
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align. Also make sure that the protective baffle in the top half of the case, which keeps the copper ground ring in its place, aligns properly with the ring itself.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.

{{Info|For normal operation of the iron, omission of the copper ring in step #2 does not impact operation. If you are working with ESD components, you need it in order to ground the iron tip via the earth screw at the back of the iron. It is recommended to keep this installed.}}

{{Warning|Make sure that the copper ground ring in step #2 is installed so it fits flush with the grounding metal insert in the bottom half of the case. Failure to do so may cause the copper ground ring touch one of the copper tip contacts in step #6, which may later cause damage to some of the components on the PCB.}}

== FAQ ==

=== Common Fixes ===

# Sometimes, just updating to the newest firmware fixes issues as Ralim and team are very active in adding features and <s>bug fixes</s> enhancements (see [[Pinecil#Firmware_&_Updates| Firmware]]).
# Some [https://ralim.github.io/IronOS/Troubleshooting/ Troubleshooting information] is also on GitHub Ralim's IronOS (which is the firmware that is on the Pinecil). There are several hidden Debug tools in the firmware that also help with diagnosis.
# Clean all new Tips (Cartridges) with 90%-99% IPA (Isopropyl Alcohol) especially the white end with the 2 silver contacts.
# If you can't find the information here or it hasn't been written yet; simply join the volunteer run [[Pinecil#Live_Community_Chat| live Pinecil chat channel]]. Sometimes you can get a clue to the right path.

=== Common Questions ===

# '''Temperature is flickering wildly''':
#* Most likely just need to clean whole cartridge/tip with IPA ([https://github.com/Ralim/IronOS/issues/1601 reference issue]). See [[#Poor_Contact_Fix|Poor Contact Fix here]].
#* If it's jumping wildly after reaching set temperature, this is also caused by using a low amp/volt charger that is below the 3amp minimum required for pinecil (per manufacturer rating), upgrading to a 3.25amp/20V USB-C charger often fixes this ([https://github.com/Ralim/IronOS/issues/1644 reference issue]).
#* Some people might see a random spike while idle. Solution: update firmware, there are some ADC timing adjustments in IronOS 2.21+; it's a good idea to keep your firmware updated to newest stable release ([https://github.com/Ralim/IronOS/issues/1485 reference issue]). This fix is included in 2.21+ release.
# '''Screen shows X symbol''' (no tip installed) and I have a tip installed. Ensure the cartridge/tip is properly installed: remove the front Tip screw, check that the cartridge/tip is pushed all the way in and the round metal collar is pressed against the black handle [https://wiki.pine64.org/wiki/File:Pinecilv2-1.jpg see photo here]. Reinstall the screw. See [[#Tip_Problems|Tip Problems]] and [[#Poor_Contact_repair|Poor Contact repair]].
# '''Screen shows the symbol (X) randomly on new Pinecil''': tip is installed and it heats up and works fine, but randomly I see the no tip symbol (X) come and go for a second. See #1 above, it is most likely the same reason, clean the metal contacts on the rear of the cartridge/tip (even if it looks clean, could have residue/oils). Follow the same instructions for [[#Poor_Contact_Fix|Poor Contact Fix here]]. [https://github.com/Ralim/IronOS/issues/1601 Reference ticket on Github].
# '''How do I install the optional Hall Effect Sensor?''' See the [[Pinecil_Hall_Effect_Sensor| Hall Effect Sensor]] article for installation; location is U14 on the PCB & in the Schematics. Reference schematics section [[#Schematics_and_Board_Data| here]] also.
# '''Help, I think I bricked Pinecil doing an update''': no worries, it's very hard to brick a Pinecil because of the way the firmware is loaded in ROM. Usually just flashing again with a newer or different version brings it back to life ([[Pinecil#Firmware_&_Updates|see Firmware]]). This can be done even if you can't see your screen anymore.
# '''My Pinecil keeps rebooting''': some laptop ports are not compatible to do updates and show pinecil screen rebooting, change to a different ports on the laptop or different machine (e.g., sometimes the USB-A port works where the usb-C did not). If it is rebooting connected to a power charger, change to a different charger or add a ground wire to your Pinecil ground screw (search for ''ts100 ground wire'' on a search engine). Also see the [[Pinecil#Power_Supplies_and_Watts|Power Supplies article]]. This could happen because of the way 2-prong no-ground chargers are made with no ground path for small current leakage. Also try to plug the charger into a surge protector strip (type that have 3-prong ground and plug the surge protector into a 3-prong grounded wall outlet). Try a different cable or flipping the cable over also.
# '''Tip is glowing red hot'''. Unplug immediately, you have most likely a blown MOSFET, check that out, replacement parts in Datasheets below. Tip is probably damaged too. Make sure you are using the correct rated charger for Pinecil (some cheap, universal or no-brand DC bricks can damage electronics from spiking voltages).
# '''My temperature display is way off and Pinecil is at room temerature''': first, check [[#Poor_Contact_Fix| poor contact fix here]]. Then enter the hidden debug menu and look for HAN C which is the internal handle temperature. This should normally be close to or slightly higher than the room temperature if the pinecil tip is also at room temperature. Under load, the HAN C can go up a bit, otherwise when the tip is cold, the HAN C should be close to ambient. Depending on your version of IronOS, the debug menu will show as HAN C or C Han. See IronOS [https://ralim.github.io/IronOS/Troubleshooting/ Troubleshooting here], especially about CHan and the Temperature sensor. If the reading is out of spec (very low/high), and reflowing/resoldering the Temperature sensor does not work, replacement might be needed.
# '''I see <code>Thermal Runaway</code> or <code>Undervoltage</code> messages on the screen'''. This is often caused by using a weak power supply that does not have a minimum of 12V-3amps and is not rated to work with Pinecil. Pinecil will stop heat to the tip and display <code>Thermal Runaway</code>.
#* TL;DR get a USB-C charger 20V 3.25 amps, PD 65W (best bang for the buck for good Pinecil performance) many available between $15-$25.
#* Detailed information on chargers and suggested types is in the article [[Pinecil Power Supplies]].
# '''I plugged in the wrong kind of DC barrel charger, it was a not Center-positive pin and now the Pinecil won't turn on''': see [[#Reverse_polarity_damage| Reverse polarity damage]]. Usually requires replacing the MOSFET (U13) and Buck Converter/Step-down (U8). See the datasheets for links to parts.
# '''I hear a sizzling/crackle sound from my new Pinecil''': this small noise is usually fine and may disappear after a few days of use, see [[#Hissing_Crackle_Sound| Hissing Crackle Sound]].
# '''Screen is black''': first try to update firmware. Check out the IronOS troubleshooting [https://ralim.github.io/IronOS/Troubleshooting/#no-display-or-dots-on-the-display guide here] for possible issues. See the [[#Datasheets_for_Components|datasheets here]] at the bottom of this article for links to replacement parts. Repair method would be similar to ts100 screens of which there are many guides like [https://www.youtube.com/watch?v=HlWAY0oYPFI this video]. If the tip heats up, but screen is black, the OLED may have failed/burned out. If tip does not heat up, it may be something else. Sometimes just reflow/reheat the solder for the OLED screen fixes issues. Using OLED screen at lower brightness extends the life.

== Solutions ==

=== Hissing Crackle Sound ===

# The sizzle sound will usually go away after a few days of use and heating up the iron. First, clean the tip contacts (at the white end of the cartridge) with IPA (isopropyl alcohol), heat it up a few times to 350 °C to break it in (add solder to the tip to protect it).
# Ralim said, "there is usually a bit of noise when you first use it, and a slight hiss/pop noise from the handle and that is normal. depends a bit on exactly what batch of caps are in your unit. The Tip drive signal is AC coupled through a capacitor for safety, downside is that it means the firmware is hitting that cap with a square wave the whole time the tip is on. Once you have heated up the duty cycle, it drops off so it's not as noticeable."
# Some members reported that after they opened their new Pinecil, wiped the PCB and tips gently with IPA, let it dry, all the sizzling noise went away. They also did a break-in of the new tips, bringing the temperature to 350 C a few times.
# Video of similar [https://www.reddit.com/r/soldering/comments/qv66a6/weird_crackling_noise_from_ts100_not_from_the_hot/ crackle sound] on the ts100 iron (don't have example of Pinecil, but it's similar sound).

=== Cartridge/Tip Problems ===

# Wipe entire tip (cartridge) clean, details in [[#Poor_Contact_test_and_repair|Poor Contact]] section
# Using a multimeter, switch it to ohms to measure resistance. Measure the two silver bands at the rear (white end).
# If it measures OL or infinity, or extremely out of the spec range below, it might be bad.
# Note, only measure when cartridge/tip is cold and unused for a couple hours (a warm tip will have much higher resistance/ohm reading).
#* Normal ts100 style tips should measure ~7.8 ohms - 8.3 ohms (when cold)
#* PINE64 brand Short tips should measure ~6.1-6.5 ohms (when cold).
#* See the [[Pinecil Tips]] for more details.

=== Poor Contact Fix ===

[[File:CleanTip-Cartridge-Contacts.jpg|none|300px|thumb| Clean contacts with IPA]]

# Most likely the tip (cartridge) is not making good contact (at the silver bands on the rear white end). Usually this issue goes away after a few days of use as the cartridge rubs against the internal contacts more. New cartridges could have factory residue or oils on them that interferes with the R-tip reading.
# To fix this issue quicker, wipe all new tips (cartridges) with a dry towel or 90-99% IPA (isopropyl alcohol) especially the two silver contacts at the white end (do not use water to wipe as it could get into the seam line on the white end).
# With the Pinecil unplugged, remove and reinsert the tip a couple times and spin it a little inside against the contacts. Then plug it in and heat it up to 350 °C a few times for a couple minutes. These steps tend to resolve most new Pinecil or new cartridges causing flickering temperatures or "no-tip" icon displays randomly.
# Always unplug Pinecil before swapping tips. Hot swapping is not a good idea, and for the V2 this could cause strange behavior as the V2 auto-detects tip resistance only on power-up or reboot.
# Sometimes just disassembling and reassembling all parts back correctly and installing the 2 internal contacts with screws correctly also helps.
# Poor contact could happen if the tips are not clean or brand new with factory residue or not making good contact with the internal clips inside the Pinecil. The two contacts inside might need to also be removed, wiped and reinstalled with the two screws (ensure the small metal tab on the clip sits into the small hole in the PCB).
# See '''[[Pinecil_Tips#How_to_check_new_tips?| Pinecil Tips]]''' article for more details on testing.

=== Not Powering Up Anymore ===

There are reports
([https://forum.pine64.org/showthread.php?tid=12661 #1],
[https://www.reddit.com/r/PINE64official/comments/q8d08a/pinecil_does_not_power_on/ #2])
that Pinecil that has been working stopped powering on. Note this is different from black screen issue mentioned above - in this case, Pinecil simply does not power on and also does not recognized as an USB device. Also, it is not an USB-PD compatibility issue as the device has been working fine up until this issue.

It has been reported that dead USB-PD controller (FUSB302MPX) was the cause. While the root cause of the failure is still unknown, Pinecil can be 'repaired' by removing the chip, allowing it to be used as a DC-powered soldering iron. Removing FUSB302MPX (small 5x5mm QFN) requires some effort, but it is doable by careful desoldering (or hotair desoldering).

=== Reverse Polarity Damage ===

Pinecil requires a center-positive DC power supply which most are, but some are reverse polarity and will destroy the electronics if used. If you plugged in a "center-negative" DC power supply, most likely the MOSFET and the buck converter are broken. This usually requires replacing the MOSFET (U13) and buck converter / step-down (U8). See the datasheets for links to replacement parts which is at the bottom of this article [[#Datasheets_for_Components| here]].

{{Note|1='''Check the polarity''' of the DC barrel plug before plugging in a random charger. Incorrect polarity will break the Pinecil. The [https://www.youtube.com/watch?v=5DBTNplNTfA video here] shows how to check.}}

[[File:AC adaptor polarity.png|400px]]

[[File:Nintendo-center-negative.png|300px]]

Reference the article on [[Pinecil_Power_Supplies#DC_Barrel_Power| DC barrel chargers here]], (i.e., laptop bricks) for appropriate USB-C and DC chargers that will work with the Pinecil.

== Images ==

<gallery mode="packed">
Image:PCP-Top-side-screen.jpg|Screen side: V2 on top, V1 below
Image:PCP-Bottom-Side.jpg|Pinecone side: V2 on top, V1 below
File:Pinecil v2 MOSFET.JPG | MOSFET V2 |alt=alt language
File:FUSB302-V2-02.JPG | FUSB302 V2 |alt=alt language
File:Pinecil LDOandOP-Amp.png| LDO and OP-Amp|alt=alt language
File:Under OLED screen01.png| Under the OLED screen, V2|alt=alt language
</gallery>

== Schematics and Board Data ==

=== Pinecil V2 mainboard schematic ===

* [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v2.0_20220608.pdf Pinecil mainboard schematic ver 2.0 20220608, this is production version schematic]
* [https://files.pine64.org/doc/Pinecil/Pinecil_PCB_placement_v2.0_20220608.pdf Pinecil mainboard ver 2.0 PCB Component Placement PDF file]

=== Pinecil V1 mainboard schematic ===

V1 was only sold until July 2022, and then discontinued for newer V2 model

* [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

== Datasheets for Components ==

=== Pinecil V2 datasheets ===

* Power MOSFET Switch: [https://datasheet.lcsc.com/lcsc/2105241831_HUASHUO-HSM4313_C2828487.pdf HSM4313], location U13 (replacement [https://lcsc.com/product-detail/MOSFETs_HUASHUO-HSM4313_C2828487.html HSM4313])
* LDO Regulator: [https://datasheet.lcsc.com/lcsc/1912111437_LOWPOWER-LP3986-33B3F_C387689.pdf LP 3986-33], Ultra-low noise, location U5 (replacement [https://www.lcsc.com/product-detail/Linear-Voltage-Regulators-LDO_LOWPOWER-LP3986-33B3F_C387689.html LP 3986-33])
* Buck Converter: [https://datasheet.lcsc.com/lcsc/2108072230_TECH-PUBLIC-TP6841S6_C2844736.pdf TP6841S6 40V], Step-Down, location U8 (replacement [https://www.lcsc.com/product-detail/DC-DC-Converters_TECH-PUBLIC-TP6841S6-A_C2844924.html TP6841S6-A])
* USB-C PD Controller: [https://rocelec.widen.net/view/pdf/0av2cqef3a/FAIR-S-A0001311862-1.pdf?t.download=true&u=5oefqw FUSB302MPX], location U1 (replacement [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-ICs_onsemi-Fusb302mpx_C442699.html FUSB302MPX])
* Acceleration/Gyroscope: [https://lcsc.com/product-detail/Attitude-Sensor-Gyroscope_Hangzhou-Silan-Microelectronics-SC7A20TR_C5126709.html SC7A20 sensor], Silan, location U9 (replacement unknown)
* NTC Temperature Sensor: [https://media.digikey.com/pdf/Data%20Sheets/TDK%20PDFs/NTCG163JF103FTDS_Spec.pdf NTCG163JF103FTDS], location NTC1 (replacement [https://lcsc.com/product-detail/span-style-background-color-ff0-NTC-span-Thermistors_TDK-NTCG163JF103FTDS_C435270.html NTC here]). Note that U10 is empty if NTC type thermistor is used.
* Optional Hall Effect Sensor: [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Si7210-B-00-IV(R)] by Silicon Labs, location U14. This is a user add-on and does not come installed on the PCB.
** [https://www.silabs.com/documents/public/application-notes/an1018-si72xx-sensors.pdf How magnets work near Hall Sensor Si7210]
** Replacement [https://lcsc.com/product-detail/Position-Sensor_SILICON-LABS-SI7210-B-00-IVR_C2654956.html Si7210-B-00-IV], also at Digikey and Mouser
* Operational Amplifier [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGM8557-1AXN5G], SGMicro, Low Noise OP Amp Datasheet, location U11 (replacement unknown).
* Display Screen OLED [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG-9616TSWCG02] datasheet (replacement [https://www.lcsc.com/product-detail/OLED-Displays-Modules_UG-Univision-Semicon-UG-9616TSWCG02_C88335.html QUG-9616TSWCG02] OLED Display).

MCU: Bouffalo Labs, BL-706_QFN48, RISC-V + 2.4 GHz RF SoC
* [https://lupyuen.github.io/articles/bl706 BL706 Analysis], by Lupyuen, includes datasheet, location U15.
* [https://dev.bouffalolab.com/media/doc/702/open/datasheet/en/html/index.html BL706 datasheet] and its [https://github.com/bouffalolab/bl_docs/blob/main/BL702_DS/en/BL702_704_706_DS_en_2.6.pdf PDF version]
* [https://dev.bouffalolab.com/media/doc/702/open/reference_manual/en/html/index.html BL706 Reference Manual] and its [https://github.com/bouffalolab/bl_docs/blob/main/BL702_RM/en/BL702_BL704_BL706_RM_en_1.2.pdf PDF version]
* [https://github.com/bouffalolab/bl_mcu_sdk SDK and Bouffalo documents]
* [https://datasheet.lcsc.com/lcsc/1912111437_TAE-Zhejiang-Abel-Elec-TAXM32M4ZFBCCT2T_C388797.pdf SMD Resonator] for Bluetooth BLE, 32MHZ/12PF-10PPM, SMD2016-4P, location UX1 (replacement [https://lcsc.com/product-detail/Crystals_TAE-Zhejiang-Abel-Elec-TAXM32M4ZFBCCT2T_C388797.html SMD Resonator]).

USB-C port:
* possible part, has not been verified: [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-Connectors_SHOU-HAN-TYPE-C-24P-QT_C2681555.html Replacement USB-C port]

=== Pinecil V1 datasheets ===

* Buck converter: [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf RT7272B 3A Datasheet], Ricktek, Step-Down converter, location U8
* LDO Regulator: [https://datasheet.lcsc.com/lcsc/1912111437_LOWPOWER-LP3986-33B3F_C387689.pdf LP 3986-33], location U5, ([https://www.lcsc.com/product-detail/Linear-Voltage-Regulators-LDO_LOWPOWER-LP3986-33B3F_C387689.html Replacement here]).
* MOSFET Switch: [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf CJQ7328 8A datasheet], Chang Jiang.
** Hint: people have replaced V1 mosfet using the better rated one from the newer V2 datasheets (HSM4313 has same footprint and higher rating), see V2 section for MOSFET.
* Acceleration [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Sensor Datasheet]
* Temperature Sensor: [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Datasheet], location U10, (possible [https://www.lcsc.com/product-detail/Temperature-Sensors_Analog-Devices-TMP36GRTZ-REEL7_C129489.html replacement here]).
* Optional Hall Effect Sensor: [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Si7210-B-00-IV(R) by Silicon Labs, location U14]. This is a user add-on and does not come installed on the pcb.
** ([https://www.silabs.com/documents/public/application-notes/an1018-si72xx-sensors.pdf How magnets work near Hall Sensor Si7210])
** ([https://lcsc.com/product-detail/Position-Sensor_SILICON-LABS-SI7210-B-00-IVR_C2654956.html One place to buy it], also at Digikey and Mouser)
* OLED Display screen: [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller: [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF FUSB302 USB PD Datasheet]
* OP Amp information: [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet (U11)]
* Capacitors: [https://lcsc.com/product-detail/Multilayer-Ceramic-Capacitors-MLCC-SMD-SMT_YAGEO-CC0603KRX7R9BB105_C559769.html possible replacement part for C5, 1uF/50V]
* USB-C port: possible part, has not been verified: [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-Connectors_SHOU-HAN-TYPE-C-24P-QT_C2681555.html Replacement]

GigaDevice RISC-V SoC data:

* [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
* [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]

Breakout Board Datasheet: [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LP6498B6F 1.2A Switching Power Regulator]

== Pinecil V1, 24V Mod ==

{{warning|Do this at your own risk, read everything in this section and related/linked articles, and go to the Pinecil community chat if you desire advice. An incorrect cut of the trace could render the Pinecil non-working.}}

[[File:Pinecil-V1andV2.png|350px|thumb|right| Pinecil V1 has blue rubber. Newer Pinecil V2 has green rubber & Bluetooth LE chip]]

# This modification is '''Not''' for the V2 (sold after Aug 1, 2022 with green thumb grip) as the V2 '''already''' has 24V DC barrel charger capability.
# If you have an older V1 model, then first upgrade to the newest [[Pinecil#Firmware_&_Updates|firmware here]] before starting this modification. The PD debug menu was added to the firmware in 2.17 and other important fixes came later. Access to the hidden PD debug menu is necessary to assist with this mod.
# See Ralim's IronOS for how to use the hidden [https://ralim.github.io/IronOS/DebugMenu/#pd-debug-menu PD Debug here] and check if your version of Pinecil V1 could benefit from the modification.
# If PD-Debug menu says "No VBUS", then stop here, you do not need the modification or any cut of the trace line, it will not benefit you because there is no connection to the VBUS already. If it says "w. Vbus" then continue. If you don't have a PD-Debug menu, then upgrade to the newest firmware first, see instructions above.
# Some models of V1 came with the PCB already capable of 24V as the Pine Store made modifications to the PCB (not all batches of V1 were the same). Do the PD debug test first to see if the mod is not required.
# See the February 2022 [https://www.pine64.org/2022/02/15/february-update-chat-with-the-machine/ Community update here]. The photo is incorrect in the article. It is ''not'' a before and after photo.
#* Photo shows two separate PCBs of Pinecil V1 made at different times; therefore, the trace is cut in a slightly different location depending on which one it looks like.
#* The PCB with 2 small via holes and is harder to cut in the correct location to avoid damaging the holes. This is called the "whalecil" in community chat (looks like a whale).

[[File:Pinecil V1 24V Mod.png|400px]]

PCB 1 style (left photo) is easier to cut the trace. Cut all the way across the trace and deep enough to cut the copper contact. PCB 2 style (right photo) is harder because the trace has to be cut without damaging the 2 via holes.

7. Don't plug in 24V until you first check with a USB-C PD charger that PD debug says '''No VBUS''' which means the mod is complete. If it still says '''W. Vbus''', then the connection still exist. Cut a little deeper and clean the cut with some IPA (isopropyl alcohol) to remove any copper dust, dry it and check again. Taking a macro photo with a phone helps to examine the cut.
If a USB-C charger is not available, often a phone with a USB-C port is a PD type, and can be used like a charger to plug in and check the PD debug messages (unfortunately, a PC port is not normally "PD" and won't give proper PD Debug).

8. If you want another set of eyes on it before you cut, post a photo of your PCB (near the Pinecone) on the Pine64 > [[Pinecil#Live_Community_Chat|live Pinecil chat channel]]. Ask for a volunteer who has ''completed'' the 24V mod on a Pinecil V1 to assist. Not all chat people own a Pinecil even if they are in the Pinecil channel.

[[Category:Pinecil]]

Pinecil: Test, Repair, Issues

2024-11-16T20:02:56Z

Dsimic: /* Assemble steps */ Minor wording tweak

This article explains some common issues and fixes which includes how to dismantle, test and do some repairs.

== Cautions ==

{{warning| while opening your Pinecil will not necessarily void your warranty, all self-repairs are '''done at your own risk'''. Read everything in this section and related or linked articles to get a good idea of the procedure, and go to the Pinecil community chat if you desire advice/support from experienced volunteers. Self-repairs or modifications might void your warranty so proceed if this is not a concern. This information is for educational purposes only.}}

Pinecil V1 and V2 have slightly different schematics and have different MCU chips. Doing repairs often requires referencing the correct schematics or photos. The datasheets are also important to get information about the chips, and to order replacement parts. The schematics and known datasheets are all at the bottom of this article and linked in the contents table at the top. Chatting with other owners of Pinecil is encouraged as they have experience - already broke things so you don't have to (see Pinecil volunteer [[Pinecil#Live_Community_Chat |chat link here]]).

{{Info|This is a new work in progress (WIP) started Feb. 18, 2023 which may be updated over time as volunteers have time to write up information. For sections that are missing, try asking in the live chat as a volunteer may have some clues to get you headed in the right path.}}

== Tools needed ==

# Digital multimeter (DMM)
# Philips screwdriver
# All schematics, datasheets for known common parts, and links to where to buy replacement parts are all in this article under [[#Schematics_and_Board_Data| Schematics and board data]].
#* Refer to the correct section for V1 or V2 parts.
#* Which model do I have? The older V1 model has an all black handle with a blue silicone grip and was discontinued in July 2022. The new V2 model has a black handle with a green thumb grip and is the only model PINE64 and authorized resellers started selling after August 1, 2022.
# Magnifying lamp or jeweler's glasses with led light and good room light.
# Photos/videos will help to chat with volunteers in the [[Pinecil#Live_Community_Chat|live Pinecil chat channel]] if getting clarification or troubleshooting.
# Optional: mobile phone to take macro photos or video. A macro lens to take phone photos is helpful; there are cheap ones that simply clip on.
# Possibly another soldering iron to do the repair, some flux, solder, and isopropyl alcohol (IPA) for cleaning the PCB. See [[Pinecil_Cases,_Stands,_Supplies#Soldering_supplies| this guide]] for some basic supply options.
# Optional: better needle size probe leads for DMM makes things easier and are nice for electronic work.
# Reference photos are in the [[#Images| Images section below]].

== Dismantle steps ==

=== Easy trick to open Pinecil ===

* Video of easy trick: https://www.youtube.com/watch?v=aK01V5DrrVk

* Handle replacement [https://wiki.pine64.org/wiki/File:Pinecil_Shell_Replacement_Guide.pdf graphic]

* Step-by-step

# It is recommended to take photos to help with reassembly.
# Loosen the top tip screw (PH1) (top is the side with the screen).
# Gently pull the tip out and set aside (let the tip cool down first or use protection to prevent burns).
# Slide the rubber thumb grip off the front.
# Remove the bottom-front screw (between the bottom feet (PH1)).
# Remove the ground screw (longer m2x4mm screw next to the screen near the (-) button (PH1)).
# Slightly pull the two halves of the case apart at the tip front end first, enough to get a fingernail or guitar pick between 2 parts.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by sliding it a little forward (it is retained by the top half at the DC barrel side).
# Remove the screws retaining the copper tip contacts (PH000, M1.4 x 5).
# Remove the copper tip contacts (note the orientation of the contacts & tiny tab hole).
# Lift the PCB gently up from Tip end.
# Remove the round copper ring contact from under the PCB, near the tip end of the handle (this is installed first before the PCB because it provides ground contact from the front of the Pinecil to the rear ground screw).
# Remove the two small round buttons so they do not get lost.

== Assemble steps ==

# Place the two round buttons into the two holes in the top half of the case.
# Install the round copper ground ring at the tip end '''before installing the PCB'''.
# Place the PCB board into handle at an angle, DC barrel end goes in first.
## Lower the rest of the board into the case and align the PCB with the two contact screw holes.
# Install the two copper tip contacts (note the small tab on the contact and the small hole in the PCB for it).
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.
{{Info| For normal operation of the iron, omission of the copper ring in step #2 does not impact operation. If you are working with ESD components, you need it in order to ground the iron tip via the earth screw at the back of the iron. It is recommended to keep this installed.}}

== FAQ ==

=== Common Fixes ===

# Sometimes, just updating to the newest firmware fixes issues as Ralim and team are very active in adding features and <s>bug fixes</s> enhancements (see [[Pinecil#Firmware_&_Updates| Firmware]]).
# Some [https://ralim.github.io/IronOS/Troubleshooting/ Troubleshooting information] is also on GitHub Ralim's IronOS (which is the firmware that is on the Pinecil). There are several hidden Debug tools in the firmware that also help with diagnosis.
# Clean all new Tips (Cartridges) with 90%-99% IPA (Isopropyl Alcohol) especially the white end with the 2 silver contacts.
# If you can't find the information here or it hasn't been written yet; simply join the volunteer run [[Pinecil#Live_Community_Chat| live Pinecil chat channel]]. Sometimes you can get a clue to the right path.

=== Common Questions ===

# '''Temperature is flickering wildly''':
#* Most likely just need to clean whole cartridge/tip with IPA ([https://github.com/Ralim/IronOS/issues/1601 reference issue]). See [[#Poor_Contact_Fix|Poor Contact Fix here]].
#* If it's jumping wildly after reaching set temperature, this is also caused by using a low amp/volt charger that is below the 3amp minimum required for pinecil (per manufacturer rating), upgrading to a 3.25amp/20V USB-C charger often fixes this ([https://github.com/Ralim/IronOS/issues/1644 reference issue]).
#* Some people might see a random spike while idle. Solution: update firmware, there are some ADC timing adjustments in IronOS 2.21+; it's a good idea to keep your firmware updated to newest stable release ([https://github.com/Ralim/IronOS/issues/1485 reference issue]). This fix is included in 2.21+ release.
# '''Screen shows X symbol''' (no tip installed) and I have a tip installed. Ensure the cartridge/tip is properly installed: remove the front Tip screw, check that the cartridge/tip is pushed all the way in and the round metal collar is pressed against the black handle [https://wiki.pine64.org/wiki/File:Pinecilv2-1.jpg see photo here]. Reinstall the screw. See [[#Tip_Problems|Tip Problems]] and [[#Poor_Contact_repair|Poor Contact repair]].
# '''Screen shows the symbol (X) randomly on new Pinecil''': tip is installed and it heats up and works fine, but randomly I see the no tip symbol (X) come and go for a second. See #1 above, it is most likely the same reason, clean the metal contacts on the rear of the cartridge/tip (even if it looks clean, could have residue/oils). Follow the same instructions for [[#Poor_Contact_Fix|Poor Contact Fix here]]. [https://github.com/Ralim/IronOS/issues/1601 Reference ticket on Github].
# '''How do I install the optional Hall Effect Sensor?''' See the [[Pinecil_Hall_Effect_Sensor| Hall Effect Sensor]] article for installation; location is U14 on the PCB & in the Schematics. Reference schematics section [[#Schematics_and_Board_Data| here]] also.
# '''Help, I think I bricked Pinecil doing an update''': no worries, it's very hard to brick a Pinecil because of the way the firmware is loaded in ROM. Usually just flashing again with a newer or different version brings it back to life ([[Pinecil#Firmware_&_Updates|see Firmware]]). This can be done even if you can't see your screen anymore.
# '''My Pinecil keeps rebooting''': some laptop ports are not compatible to do updates and show pinecil screen rebooting, change to a different ports on the laptop or different machine (e.g., sometimes the USB-A port works where the usb-C did not). If it is rebooting connected to a power charger, change to a different charger or add a ground wire to your Pinecil ground screw (search for ''ts100 ground wire'' on a search engine). Also see the [[Pinecil#Power_Supplies_and_Watts|Power Supplies article]]. This could happen because of the way 2-prong no-ground chargers are made with no ground path for small current leakage. Also try to plug the charger into a surge protector strip (type that have 3-prong ground and plug the surge protector into a 3-prong grounded wall outlet). Try a different cable or flipping the cable over also.
# '''Tip is glowing red hot'''. Unplug immediately, you have most likely a blown MOSFET, check that out, replacement parts in Datasheets below. Tip is probably damaged too. Make sure you are using the correct rated charger for Pinecil (some cheap, universal or no-brand DC bricks can damage electronics from spiking voltages).
# '''My temperature display is way off and Pinecil is at room temerature''': first, check [[#Poor_Contact_Fix| poor contact fix here]]. Then enter the hidden debug menu and look for HAN C which is the internal handle temperature. This should normally be close to or slightly higher than the room temperature if the pinecil tip is also at room temperature. Under load, the HAN C can go up a bit, otherwise when the tip is cold, the HAN C should be close to ambient. Depending on your version of IronOS, the debug menu will show as HAN C or C Han. See IronOS [https://ralim.github.io/IronOS/Troubleshooting/ Troubleshooting here], especially about CHan and the Temperature sensor. If the reading is out of spec (very low/high), and reflowing/resoldering the Temperature sensor does not work, replacement might be needed.
# '''I see <code>Thermal Runaway</code> or <code>Undervoltage</code> messages on the screen'''. This is often caused by using a weak power supply that does not have a minimum of 12V-3amps and is not rated to work with Pinecil. Pinecil will stop heat to the tip and display <code>Thermal Runaway</code>.
#* TL;DR get a USB-C charger 20V 3.25 amps, PD 65W (best bang for the buck for good Pinecil performance) many available between $15-$25.
#* Detailed information on chargers and suggested types is in the article [[Pinecil Power Supplies]].
# '''I plugged in the wrong kind of DC barrel charger, it was a not Center-positive pin and now the Pinecil won't turn on''': see [[#Reverse_polarity_damage| Reverse polarity damage]]. Usually requires replacing the MOSFET (U13) and Buck Converter/Step-down (U8). See the datasheets for links to parts.
# '''I hear a sizzling/crackle sound from my new Pinecil''': this small noise is usually fine and may disappear after a few days of use, see [[#Hissing_Crackle_Sound| Hissing Crackle Sound]].
# '''Screen is black''': first try to update firmware. Check out the IronOS troubleshooting [https://ralim.github.io/IronOS/Troubleshooting/#no-display-or-dots-on-the-display guide here] for possible issues. See the [[#Datasheets_for_Components|datasheets here]] at the bottom of this article for links to replacement parts. Repair method would be similar to ts100 screens of which there are many guides like [https://www.youtube.com/watch?v=HlWAY0oYPFI this video]. If the tip heats up, but screen is black, the OLED may have failed/burned out. If tip does not heat up, it may be something else. Sometimes just reflow/reheat the solder for the OLED screen fixes issues. Using OLED screen at lower brightness extends the life.

== Solutions ==

=== Hissing Crackle Sound ===

# The sizzle sound will usually go away after a few days of use and heating up the iron. First, clean the tip contacts (at the white end of the cartridge) with IPA (isopropyl alcohol), heat it up a few times to 350 °C to break it in (add solder to the tip to protect it).
# Ralim said, "there is usually a bit of noise when you first use it, and a slight hiss/pop noise from the handle and that is normal. depends a bit on exactly what batch of caps are in your unit. The Tip drive signal is AC coupled through a capacitor for safety, downside is that it means the firmware is hitting that cap with a square wave the whole time the tip is on. Once you have heated up the duty cycle, it drops off so it's not as noticeable."
# Some members reported that after they opened their new Pinecil, wiped the PCB and tips gently with IPA, let it dry, all the sizzling noise went away. They also did a break-in of the new tips, bringing the temperature to 350 C a few times.
# Video of similar [https://www.reddit.com/r/soldering/comments/qv66a6/weird_crackling_noise_from_ts100_not_from_the_hot/ crackle sound] on the ts100 iron (don't have example of Pinecil, but it's similar sound).

=== Cartridge/Tip Problems ===

# Wipe entire tip (cartridge) clean, details in [[#Poor_Contact_test_and_repair|Poor Contact]] section
# Using a multimeter, switch it to ohms to measure resistance. Measure the two silver bands at the rear (white end).
# If it measures OL or infinity, or extremely out of the spec range below, it might be bad.
# Note, only measure when cartridge/tip is cold and unused for a couple hours (a warm tip will have much higher resistance/ohm reading).
#* Normal ts100 style tips should measure ~7.8 ohms - 8.3 ohms (when cold)
#* PINE64 brand Short tips should measure ~6.1-6.5 ohms (when cold).
#* See the [[Pinecil Tips]] for more details.

=== Poor Contact Fix ===

[[File:CleanTip-Cartridge-Contacts.jpg|none|300px|thumb| Clean contacts with IPA]]

# Most likely the tip (cartridge) is not making good contact (at the silver bands on the rear white end). Usually this issue goes away after a few days of use as the cartridge rubs against the internal contacts more. New cartridges could have factory residue or oils on them that interferes with the R-tip reading.
# To fix this issue quicker, wipe all new tips (cartridges) with a dry towel or 90-99% IPA (isopropyl alcohol) especially the two silver contacts at the white end (do not use water to wipe as it could get into the seam line on the white end).
# With the Pinecil unplugged, remove and reinsert the tip a couple times and spin it a little inside against the contacts. Then plug it in and heat it up to 350 °C a few times for a couple minutes. These steps tend to resolve most new Pinecil or new cartridges causing flickering temperatures or "no-tip" icon displays randomly.
# Always unplug Pinecil before swapping tips. Hot swapping is not a good idea, and for the V2 this could cause strange behavior as the V2 auto-detects tip resistance only on power-up or reboot.
# Sometimes just disassembling and reassembling all parts back correctly and installing the 2 internal contacts with screws correctly also helps.
# Poor contact could happen if the tips are not clean or brand new with factory residue or not making good contact with the internal clips inside the Pinecil. The two contacts inside might need to also be removed, wiped and reinstalled with the two screws (ensure the small metal tab on the clip sits into the small hole in the PCB).
# See '''[[Pinecil_Tips#How_to_check_new_tips?| Pinecil Tips]]''' article for more details on testing.

=== Not Powering Up Anymore ===

There are reports
([https://forum.pine64.org/showthread.php?tid=12661 #1],
[https://www.reddit.com/r/PINE64official/comments/q8d08a/pinecil_does_not_power_on/ #2])
that Pinecil that has been working stopped powering on. Note this is different from black screen issue mentioned above - in this case, Pinecil simply does not power on and also does not recognized as an USB device. Also, it is not an USB-PD compatibility issue as the device has been working fine up until this issue.

It has been reported that dead USB-PD controller (FUSB302MPX) was the cause. While the root cause of the failure is still unknown, Pinecil can be 'repaired' by removing the chip, allowing it to be used as a DC-powered soldering iron. Removing FUSB302MPX (small 5x5mm QFN) requires some effort, but it is doable by careful desoldering (or hotair desoldering).

=== Reverse Polarity Damage ===

Pinecil requires a center-positive DC power supply which most are, but some are reverse polarity and will destroy the electronics if used. If you plugged in a "center-negative" DC power supply, most likely the MOSFET and the buck converter are broken. This usually requires replacing the MOSFET (U13) and buck converter / step-down (U8). See the datasheets for links to replacement parts which is at the bottom of this article [[#Datasheets_for_Components| here]].

{{Note|1='''Check the polarity''' of the DC barrel plug before plugging in a random charger. Incorrect polarity will break the Pinecil. The [https://www.youtube.com/watch?v=5DBTNplNTfA video here] shows how to check.}}

[[File:AC adaptor polarity.png|400px]]

[[File:Nintendo-center-negative.png|300px]]

Reference the article on [[Pinecil_Power_Supplies#DC_Barrel_Power| DC barrel chargers here]], (i.e., laptop bricks) for appropriate USB-C and DC chargers that will work with the Pinecil.

== Images ==

<gallery mode="packed">
Image:PCP-Top-side-screen.jpg|Screen side: V2 on top, V1 below
Image:PCP-Bottom-Side.jpg|Pinecone side: V2 on top, V1 below
File:Pinecil v2 MOSFET.JPG | MOSFET V2 |alt=alt language
File:FUSB302-V2-02.JPG | FUSB302 V2 |alt=alt language
File:Pinecil LDOandOP-Amp.png| LDO and OP-Amp|alt=alt language
File:Under OLED screen01.png| Under the OLED screen, V2|alt=alt language
</gallery>

== Schematics and Board Data ==

=== Pinecil V2 mainboard schematic ===

* [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v2.0_20220608.pdf Pinecil mainboard schematic ver 2.0 20220608, this is production version schematic]
* [https://files.pine64.org/doc/Pinecil/Pinecil_PCB_placement_v2.0_20220608.pdf Pinecil mainboard ver 2.0 PCB Component Placement PDF file]

=== Pinecil V1 mainboard schematic ===

V1 was only sold until July 2022, and then discontinued for newer V2 model

* [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
* [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

== Datasheets for Components ==

=== Pinecil V2 datasheets ===

* Power MOSFET Switch: [https://datasheet.lcsc.com/lcsc/2105241831_HUASHUO-HSM4313_C2828487.pdf HSM4313], location U13 (replacement [https://lcsc.com/product-detail/MOSFETs_HUASHUO-HSM4313_C2828487.html HSM4313])
* LDO Regulator: [https://datasheet.lcsc.com/lcsc/1912111437_LOWPOWER-LP3986-33B3F_C387689.pdf LP 3986-33], Ultra-low noise, location U5 (replacement [https://www.lcsc.com/product-detail/Linear-Voltage-Regulators-LDO_LOWPOWER-LP3986-33B3F_C387689.html LP 3986-33])
* Buck Converter: [https://datasheet.lcsc.com/lcsc/2108072230_TECH-PUBLIC-TP6841S6_C2844736.pdf TP6841S6 40V], Step-Down, location U8 (replacement [https://www.lcsc.com/product-detail/DC-DC-Converters_TECH-PUBLIC-TP6841S6-A_C2844924.html TP6841S6-A])
* USB-C PD Controller: [https://rocelec.widen.net/view/pdf/0av2cqef3a/FAIR-S-A0001311862-1.pdf?t.download=true&u=5oefqw FUSB302MPX], location U1 (replacement [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-ICs_onsemi-Fusb302mpx_C442699.html FUSB302MPX])
* Acceleration/Gyroscope: [https://lcsc.com/product-detail/Attitude-Sensor-Gyroscope_Hangzhou-Silan-Microelectronics-SC7A20TR_C5126709.html SC7A20 sensor], Silan, location U9 (replacement unknown)
* NTC Temperature Sensor: [https://media.digikey.com/pdf/Data%20Sheets/TDK%20PDFs/NTCG163JF103FTDS_Spec.pdf NTCG163JF103FTDS], location NTC1 (replacement [https://lcsc.com/product-detail/span-style-background-color-ff0-NTC-span-Thermistors_TDK-NTCG163JF103FTDS_C435270.html NTC here]). Note that U10 is empty if NTC type thermistor is used.
* Optional Hall Effect Sensor: [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Si7210-B-00-IV(R)] by Silicon Labs, location U14. This is a user add-on and does not come installed on the PCB.
** [https://www.silabs.com/documents/public/application-notes/an1018-si72xx-sensors.pdf How magnets work near Hall Sensor Si7210]
** Replacement [https://lcsc.com/product-detail/Position-Sensor_SILICON-LABS-SI7210-B-00-IVR_C2654956.html Si7210-B-00-IV], also at Digikey and Mouser
* Operational Amplifier [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGM8557-1AXN5G], SGMicro, Low Noise OP Amp Datasheet, location U11 (replacement unknown).
* Display Screen OLED [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG-9616TSWCG02] datasheet (replacement [https://www.lcsc.com/product-detail/OLED-Displays-Modules_UG-Univision-Semicon-UG-9616TSWCG02_C88335.html QUG-9616TSWCG02] OLED Display).

MCU: Bouffalo Labs, BL-706_QFN48, RISC-V + 2.4 GHz RF SoC
* [https://lupyuen.github.io/articles/bl706 BL706 Analysis], by Lupyuen, includes datasheet, location U15.
* [https://dev.bouffalolab.com/media/doc/702/open/datasheet/en/html/index.html BL706 datasheet] and its [https://github.com/bouffalolab/bl_docs/blob/main/BL702_DS/en/BL702_704_706_DS_en_2.6.pdf PDF version]
* [https://dev.bouffalolab.com/media/doc/702/open/reference_manual/en/html/index.html BL706 Reference Manual] and its [https://github.com/bouffalolab/bl_docs/blob/main/BL702_RM/en/BL702_BL704_BL706_RM_en_1.2.pdf PDF version]
* [https://github.com/bouffalolab/bl_mcu_sdk SDK and Bouffalo documents]
* [https://datasheet.lcsc.com/lcsc/1912111437_TAE-Zhejiang-Abel-Elec-TAXM32M4ZFBCCT2T_C388797.pdf SMD Resonator] for Bluetooth BLE, 32MHZ/12PF-10PPM, SMD2016-4P, location UX1 (replacement [https://lcsc.com/product-detail/Crystals_TAE-Zhejiang-Abel-Elec-TAXM32M4ZFBCCT2T_C388797.html SMD Resonator]).

USB-C port:
* possible part, has not been verified: [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-Connectors_SHOU-HAN-TYPE-C-24P-QT_C2681555.html Replacement USB-C port]

=== Pinecil V1 datasheets ===

* Buck converter: [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf RT7272B 3A Datasheet], Ricktek, Step-Down converter, location U8
* LDO Regulator: [https://datasheet.lcsc.com/lcsc/1912111437_LOWPOWER-LP3986-33B3F_C387689.pdf LP 3986-33], location U5, ([https://www.lcsc.com/product-detail/Linear-Voltage-Regulators-LDO_LOWPOWER-LP3986-33B3F_C387689.html Replacement here]).
* MOSFET Switch: [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf CJQ7328 8A datasheet], Chang Jiang.
** Hint: people have replaced V1 mosfet using the better rated one from the newer V2 datasheets (HSM4313 has same footprint and higher rating), see V2 section for MOSFET.
* Acceleration [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Sensor Datasheet]
* Temperature Sensor: [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Datasheet], location U10, (possible [https://www.lcsc.com/product-detail/Temperature-Sensors_Analog-Devices-TMP36GRTZ-REEL7_C129489.html replacement here]).
* Optional Hall Effect Sensor: [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Si7210-B-00-IV(R) by Silicon Labs, location U14]. This is a user add-on and does not come installed on the pcb.
** ([https://www.silabs.com/documents/public/application-notes/an1018-si72xx-sensors.pdf How magnets work near Hall Sensor Si7210])
** ([https://lcsc.com/product-detail/Position-Sensor_SILICON-LABS-SI7210-B-00-IVR_C2654956.html One place to buy it], also at Digikey and Mouser)
* OLED Display screen: [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller: [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF FUSB302 USB PD Datasheet]
* OP Amp information: [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet (U11)]
* Capacitors: [https://lcsc.com/product-detail/Multilayer-Ceramic-Capacitors-MLCC-SMD-SMT_YAGEO-CC0603KRX7R9BB105_C559769.html possible replacement part for C5, 1uF/50V]
* USB-C port: possible part, has not been verified: [https://www.lcsc.com/product-detail/span-style-background-color-ff0-USB-span-Connectors_SHOU-HAN-TYPE-C-24P-QT_C2681555.html Replacement]

GigaDevice RISC-V SoC data:

* [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
* [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]

Breakout Board Datasheet: [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LP6498B6F 1.2A Switching Power Regulator]

== Pinecil V1, 24V Mod ==

{{warning|Do this at your own risk, read everything in this section and related/linked articles, and go to the Pinecil community chat if you desire advice. An incorrect cut of the trace could render the Pinecil non-working.}}

[[File:Pinecil-V1andV2.png|350px|thumb|right| Pinecil V1 has blue rubber. Newer Pinecil V2 has green rubber & Bluetooth LE chip]]

# This modification is '''Not''' for the V2 (sold after Aug 1, 2022 with green thumb grip) as the V2 '''already''' has 24V DC barrel charger capability.
# If you have an older V1 model, then first upgrade to the newest [[Pinecil#Firmware_&_Updates|firmware here]] before starting this modification. The PD debug menu was added to the firmware in 2.17 and other important fixes came later. Access to the hidden PD debug menu is necessary to assist with this mod.
# See Ralim's IronOS for how to use the hidden [https://ralim.github.io/IronOS/DebugMenu/#pd-debug-menu PD Debug here] and check if your version of Pinecil V1 could benefit from the modification.
# If PD-Debug menu says "No VBUS", then stop here, you do not need the modification or any cut of the trace line, it will not benefit you because there is no connection to the VBUS already. If it says "w. Vbus" then continue. If you don't have a PD-Debug menu, then upgrade to the newest firmware first, see instructions above.
# Some models of V1 came with the PCB already capable of 24V as the Pine Store made modifications to the PCB (not all batches of V1 were the same). Do the PD debug test first to see if the mod is not required.
# See the February 2022 [https://www.pine64.org/2022/02/15/february-update-chat-with-the-machine/ Community update here]. The photo is incorrect in the article. It is ''not'' a before and after photo.
#* Photo shows two separate PCBs of Pinecil V1 made at different times; therefore, the trace is cut in a slightly different location depending on which one it looks like.
#* The PCB with 2 small via holes and is harder to cut in the correct location to avoid damaging the holes. This is called the "whalecil" in community chat (looks like a whale).

[[File:Pinecil V1 24V Mod.png|400px]]

PCB 1 style (left photo) is easier to cut the trace. Cut all the way across the trace and deep enough to cut the copper contact. PCB 2 style (right photo) is harder because the trace has to be cut without damaging the 2 via holes.

7. Don't plug in 24V until you first check with a USB-C PD charger that PD debug says '''No VBUS''' which means the mod is complete. If it still says '''W. Vbus''', then the connection still exist. Cut a little deeper and clean the cut with some IPA (isopropyl alcohol) to remove any copper dust, dry it and check again. Taking a macro photo with a phone helps to examine the cut.
If a USB-C charger is not available, often a phone with a USB-C port is a PD type, and can be used like a charger to plug in and check the PD debug messages (unfortunately, a PC port is not normally "PD" and won't give proper PD Debug).

8. If you want another set of eyes on it before you cut, post a photo of your PCB (near the Pinecone) on the Pine64 > [[Pinecil#Live_Community_Chat|live Pinecil chat channel]]. Ask for a volunteer who has ''completed'' the 24V mod on a Pinecil V1 to assist. Not all chat people own a Pinecil even if they are in the Pinecil channel.

[[Category:Pinecil]]

PineNote Development/UART

2024-11-15T20:23:29Z

Dsimic: /* Stock dongle */ Ditto

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

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>

== Creating a 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.

== 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

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 ===

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 ===

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
* 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
* 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 ==

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]]

PineNote Development/UART

2024-11-15T20:22:40Z

Dsimic: /* Stock dongle */ Wording improvements

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

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 plugging directly into the PineNote's USB-C port. The dongle exposes a female USB-C port, which the user uses 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>

== Creating a 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.

== 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

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 ===

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 ===

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
* 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
* 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 ==

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]]

PineNote Development/UART

2024-11-15T20:21:01Z

Dsimic: /* Stock dongle */ Describe the presence of the USB UART adapter

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

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 was a simple device plugging directly into the PineNote's USB-C port.
The dongle exposed a female USB-C port, which the user plugged into to get UART access.
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 for purchase.

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

== Creating a 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.

== 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

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 ===

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 ===

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
* 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
* 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 ==

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]]

PineNote

2024-11-15T20:18:45Z

Dsimic: /* UART Dongle */ Describe the presence of the USB UART adapter

[[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.}}

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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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 ==

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-15T20:16:45Z

Dsimic: /* UART Dongle */ Small cleanups

[[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]]}}

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-installed firmware runs at a baud rate of 1,500,000 bps, 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.

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 ==

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-15T11:08:40Z

Dsimic: /* State of the software */ Be more specific

[[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]]}}

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 ==

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]]

PineTab-V

2024-11-15T09:06:14Z

Dsimic: /* Schematics and certifications */ Fixed a small typo

[[File:pinetabv_1.jpg|250px|thumb|right|The PineTab-V with the detachable keyboard attached]]

The '''PineTab-V''' is ''PINE64's'' first RISC-V tablet. It is based on the JH7110 64-bit RISC-V SoC. The packaging is very similar to ARM-based [[PineTab2]].

== Introduction ==
In late 2022, PINE64 announced plans to help grow the RISC-V hardware ecosystem alongside the existing ARM-based device line-up. The PineTab-V is an experimental device, which ships without an OS and without any promises. The JH7110 RISC-V SoC, and the RISC-V architecture in more general, is currently best described as having limited Linux support. You can think of it as a convenient development platform targeted at those of you interested in bringing Linux support to JH7110 and, by extension, the entire RISC-V ecosystem.

== Software ==

=== State of the software ===

The PineTab-V is an experimental device and lacks dedicated working software – it should therefore only be purchased by people interested in helping with the bring-up process of Linux and BSDs on the RISC-V architecture.

{{Warning|Do not buy the device unless you intend to use it for operating system development purposes.}}

=== Releases ===

The releases for the PineTab-V can be found under [[PineTab-V Releases]].

== Variants ==

There are currently two variants of the PineTab-V:

* PineTab-V – 4GB RAM and 64GB eMMC storage
* PineTab-V – 8GB RAM and 128GB eMMC storage

== Features ==
[[File:pinetabv_2.jpg|250px|thumb|right|Front- and backside of the PineTab-V]]
[[File:pinetabv_3.jpg|250px|thumb|right|Backside of the PineTab-V]]

Chassis:

* Dimensions: 242mm x 161mm x 9mm
* Weight: 520 grams (without keyboard), 990 grams (includes keyboard)
* Build: Metal and Plastic
* Color: Matte Black

Display:

* Type: HD IPS capacitive touchscreen, 16.7M colors
* Size: 10.1 inches
* Resolution: 1280×800 pixels, 16:10 ratio

Platform:

* Chipset: StarFive JH7110
* CPU: 64-bit Quad-core 1.5 GHz SiFive U74 RISC-V
* GPU: Imagination Technology BXE-4-32

Memory:

* Internal Flash Memory: 64GB (variant 1) or 128GB (variant 2) eMMC module
* System Memory: 4GB (variant 1) or 8GB (variant 2) LPDDR4 SDRAM
* Expansion: micro SD Card support SDHC and SDXC, up to 2TB

Camera:

* Main Camera: Single 5MP, LED Flash (chipset: Omnivision OV5648)
* Selfie Camera: Single 2MP (chipset: Galaxycore GC02M2)

Sound:

* Loudspeaker: Yes, stereo
* 3.5mm jack with mic: Yes, stereo
* Sound IC: [http://everest-semi.com/pdf/ES8316%20PB.pdf ES8316]

Wireless:

* Chipset: Realtek RTL8852BU
* WLAN: Wi-Fi 802.11 ax/ac/b/g/n, dual-band, hotspot
* Bluetooth: 5.2, A2DP

I/O:

* 1x USB 3.0 Type-C port (front side 3.0, rear side 2.0)
* 1x USB 2.0 Type-C port (also use as charging and debug port)
* 1x USB 2.0 Pogo keyboard port
* 1x microHDMI HD Video output

Battery:

* Removable Li-Po 6000mAh battery
* Charging: 15W – 5V 3A
* Model 30100140 from [https://zgszjjy.com/ zgszjjy]
* Charge IC: [https://www.ti.com/product/BQ25890H BQ25890H]
* Fuel Guage: [http://en.cellwise-semi.com/Public/assests/menu/20230314/64102656c943b.pdf CW2015CHBD]

== Schematics and certifications ==

[[File:PineTab-V-PCB.jpg|thumb|right|PineTab-V Board]]
PineTab-V mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab-V_Schematic_Ver1-20230614.pdf PineTab-V mainboard Released Schematic-20230614 ver 1.0]
* [https://files.pine64.org/doc/PineTab/PineTab-V_comp_ref_top-20230614.pdf PineTab-V PCB Component Reference location v1.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab-V_comp_ref_bottom-20230614.pdf PineTab-V PCB Component Reference location v1.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab-V certifications:
* [https://files.pine64.org/doc/cert/Pinetab-V%20FCC-SDOC%20Certificate-LCSA08013059E.pdf PineTab-V FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab-V%20CE%20RED%20Certificate-LCSA08013058E.pdf PineTab-V CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab-V%20CE%20EMC%20Certificate-LCSA08013057E.pdf PineTab-V CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab-V%20ROHS%20Report-LCSA08013061R.pdf PineTab-V ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMC Certificate]

== Tutorials ==

=== Connecting the UART adapter ===

[[File:PineTab2 USB UARTv2.jpg|thumb|right|300px|UART Adapter]]

The UART serves as a console for early boot and kernel messages, and also offers access to a root shell in the factory test image. The UART adapter allows access to the UART through the USB 2.0 Type-C port:
* Insert the UART adapter face-up in the USB 2.0 Type-C port (the USB port furthest from the power button).
* Connect a USB cable from another computer to the port on the adapter marked "DEBUG". The green LED on the adapter should light up. The other adapter port can be connected to USB power if you don't want to run the tablet on its battery.
* In a terminal window on the other computer, use ''tio'', ''screen'', ''minicom'', or another application that supports serial port communication to connect via USB serial at 115200 bit/s 8N1 (8 data bits, no parity, 1 stop bit):
*: <code>tio /dev/ttyUSB0</code>
*: <code>screen /dev/ttyUSB0 115200</code>
*: <code>minicom -D /dev/ttyUSB0 -b 115200</code>
** Install one of the above from your distribution's package manager if none are already installed.
** The device may have a different name, particularly if multiple USB serial devices are connected. On macOS it will have a name like <code>/dev/tty.usbserial-''nnnn''</code>.
** If ''Permission denied'' is reported, you may need to be added to the group that can access the port with a command like <code>sudo usermod -a -G dialout $USER</code>. Then log out and log back in or use a command like <code>newgrp dialout</code> to create a new shell in that group.
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display; if you do not need this service, try disabling it using these commands:
**: <code>sudo systemctl stop brltty-udev.service</code>
**: <code>sudo systemctl mask brltty-udev.service</code>
**: <code>sudo systemctl stop brltty.service</code>
**: <code>sudo systemctl mask brltty.service</code>

The switch on the UART adapter has no function on the PineTab-V; the boot order is controlled by the Vol-/Vol+ switches.

== Frequently asked questions ==

'''What is the Performance of the PineTab2 compared to the PineTab-V?'''

The PineTab2 is notably faster than the PineTab-V. You can see this by [https://github.com/ThomasKaiser/sbc-bench/blob/master/Results.md comparing the Quartz64 sbc-bench results to the Star64 ones]. Performance should not be a factor of consideration when purchasing a PineTab-V.

== External resources ==

* PINE64: Introduction of the PineTab-V, [https://www.pine64.org/2023/04/01/march-update-tablet-bonanza/ March Update: Tablet Bonanza!]
* PINE64: Launch of the PineTab-V [https://www.pine64.org/2023/04/10/pinetab-v-and-pinetab2-launch/ PineTab-V and PineTab2 launch]

[[Category:PineTab-V]]

PineNote

2024-11-15T09:00:13Z

Dsimic: Small wording improvements, as spotted

[[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 some issues that prevent 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]]}}

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 ==

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-15T08:58:37Z

Dsimic: /* State of the software */ Grammar

[[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 ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains some issues that prevent 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]]}}

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 ==

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-15T08:53:33Z

Dsimic: /* State of the software */ Expanded a bit, by providing the reasons

[[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 ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains some issues that prevent 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 contains 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]]}}

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 ==

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]]

PineTab2

2024-11-15T08:05:37Z

Dsimic: /* Board information, schematics and certifications */ Fixed a small typo

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes the following items:

* The PineTab2
* Short [[:File:Pinetab2 quick start guide en ger fr pl final.pdf|user guide]]
* Power cable
* The UART adapter board

Note that the UART adapter is in the same package as the power cable, in a second compartment, and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.
The external keyboard has 5 connection pins (the golden pins). four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* WiFi/Bluetooth chip BES2600:
** The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]]. There are at least two code releases available, with two respective/non-interchangeable firmware versions. The latest danctnix kernel has a pretty well working wifi driver.
** The BES2600 Bluetooth driver needs to be implemented.
** Hardware bugs - the power and reset circuitry is not properly implemented in the circuitry, so hard reset of the chip (in the theoretical case it freezes) is impossible without power cycling the whole board.
* The camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMC 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]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

LCD panel:

* [[:File:Boe-technology-th101mb31ig002-28a-datasheet-v10.pdf|BOE TH101MB31IG002-28A datasheet v1.0]]

== Tutorials and Frequently Asked Questions ==

Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

There's also [[:File:PineTab2_display_panel_disassembly_guide.pdf|PineTab2 disassembly guide]]. The disassembly is a very delicate operation, especially around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PineNote

2024-11-15T06:55:55Z

Dsimic: /* State of the software */ Linked the instructions

[[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 ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains some issues that prevent suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. 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]]}}

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 ==

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-15T06:53:31Z

Dsimic: /* State of the software */ Expanded a bit

[[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 ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains some issues that prevent suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. The required fixes are already available in the shipped Linux distribution, but they need to be 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]]}}

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 ==

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-15T06:52:50Z

Dsimic: /* State of the software */ Briefly described the factory-installed image issues

[[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 ===
{{Warning|The version of Debian-based Linux distribution shipped with the second PineNote batch contains some issues that prevent suspend-to-RAM from working correctly and make entering MaskROM mode using a magnet not possible. The required fixes are already available in the shipped Linux distribution.}}

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]]}}

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 ==

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-15T06:48:24Z

Dsimic: /* State of the software */ The current batch is already shipping

[[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 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]]}}

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 ==

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]]

Pinebook Pro

2024-11-11T17:05:19Z

Dsimic: /* Post NVMe install power limiting */ Added a warning about new parameter name

[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running Debian with MATE]]

The '''Pinebook Pro''' is a Linux and *BSD ARM laptop from PINE64. It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops.

The Pinebook Pro features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh (9,600 mAh in later batches) capacity battery, and the modularity that only an open source project can deliver with the dimensions of 329mm x 220mm x 12mm (WxDxH). Key features include the Rockchip RK3399 SoC, USB-C for data, video-out and power-in (2.5 A at 5 V), privacy switches for the microphone, BT/WiFi module, camera and expandable storage via NVMe (PCIe x4) with an optional adapter.

The Pinebook Pro is equipped with 4 GB of LPDDR4 system memory, up to 128 GB of eMMC flash storage, and 128 Mbit of SPI boot flash. The I/O includes: 1 x micro SD card reader (bootable), 1 x USB 2.0, 1 x USB 3.0, 1 x USB Type-C host with DP 1.2 and power-in, PCI Express x4 for an M.2 NVMe SSD drive (requires an optional adapter), and serial console UART (via the headphone jack by setting an internal switch). The keyboard and touchpad both use the USB 2.0 protocol. The LCD panel uses the eDP MiPi display protocol.

== Software and OS Image Downloads ==

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of GNU/Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

=== Default Manjaro KDE Desktop Quick Start ===

When you first get your Pinebook Pro and boot it up for the first time, it'll come with Manjaro using the KDE desktop. The Pinebook Pro is officially supported by the Manjaro ARM project, and support can be found on the [https://forum.manjaro.org/c/manjaro-arm/78 Manjaro ARM forums.]

On first boot, it will ask for certain information such as your timezone location, keyboard layout, username, password, and hostname. Most of these should be self-explanatory. Note that the hostname it asks for should be thought of as the "codename" of your machine, and if you don't know what it's about, you can make something up (use a single word, all lower case, no punctuation, e.g. "pbpro").

After you're on the desktop, be sure to update it as soon as possible and reboot after updates are finished installing. If nothing appears when you click on the Networking icon in your system tray to connect to your Wi-Fi, ensure the Wi-Fi [[#Privacy Switches|privacy switch]] is not disabled.

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

=== Linux, the kernel, downstream source ===
Although the current upstream version boots and works, the development of new features and other improvements is still ongoing. The results (including detailed changelogs) are published on [https://github.com/megous/linux/tags megi's tree].

=== Hardware-accelerated video decoding ===
Drivers for accelerated video decoding are available in the current kernels but to use the ''v4l2-request'' API with ''FFmpeg'' (and the apps that depend on it) one needs to build [https://github.com/jernejsk/FFmpeg/branches a fork]. With ''mpv'' built against it and the integrated ''yt-dlp'' support watching YouTube and similar sources is possible without stressing the CPU. Read more at [[Mainline Hardware Decoding]].

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and touchpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, touchpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware binary can be flashed from userspace using the provided open source utility.

{{warning|DO NOT update the keyboard firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a ''SH61F83'' instead of a ''SH68F83''. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when step 1 is flashed, see the [https://reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread]. The keyboard IC corresponds to ''U23'' on the [[#Pinebook_Pro_Schematics_and_Certifications|top layer silkscreen of the main board]]. It is located under the keyboard flat flexible cable.}}

Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]] and details regarding the assembly can be found under [[Pinebook Pro Keyboard Assembly]].

=== Typing special characters ===
The UK ISO Layout does not have dedicated keys for characters like the German umlauts (Ä, Ö, Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.

{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[AltGr]+'[' followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
! Notes
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch
| CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch
| NUM lock LED blinks. 2 blinks = WiFi enabled / privacy switch disabled, 3 blinks = WiFi disabled / privacy switch enabled.
| Re-enabling requires reboot (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch
| CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
| Can use tools like <code>lsusb</code> to detect camera's presence. If not detected, check privacy switch.
|}

(Press the PINE64 logo key plus F10/F11/F12) for 3 seconds)

The keyboard operates on firmware independent of the operating system. It detects if one of the F10, F11 or F12 keys is pressed in combination with the Pine key for 3 seconds. Doing so disables power to the appropriate peripheral, thereby disabling it. This has the same effect as cutting off the power to each peripheral with a physical switch. This implementation is very secure, since the firmware that determines whether a peripheral gets power is not part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots inside the keyboard's firmware flash memory.

=== Basic summary of replacing keyboard ===

This guide is very basic and should be fleshed out with (better) pictures. There just isn't a list of steps anywhere else yet.

Here's what the replacement keyboard looks like:

[[File:Pinebook_Pro_new_keyboard-front.jpg|300px|Replacement keyboard (front)]]
[[File:Pinebook_Pro_new_keyboard-front.jpg|300px|Replacement keyboard (back)]]

''Step 0'': If changing from ISO keyboard to ANSI keyboard, or vice versa, be sure to have a system capable of running the firmware updater that you can access either remotely or with a USB keyboard beyond the internal keyboard, as the firmware for each is very different and keys won't work correctly. See https://forum.pine64.org/showthread.php?tid=8407 (and for NetBSD, https://forum.pine64.org/showthread.php?tid=8716).

''Step 1'': The remove back back panel.

There are 10 screws on the back that must be removed, and the back panel detached. I recommend using a PH0 bit. The speakers may remain attached via glue to the case and should be carefully pried off. When this is done, taking photos of how everything looks now can help put it all back together later.

[[File:Pinebook_Pro_keyboard-replacement-screws.jpg|300px|Remove the back panel]]

''Step 2'': Places to unscrew.

There are 3 items screwed into the keyboard frame that must be removed. There are 2 large screws for daughter board, 3 large screws and 1 small screw for mainboard, and 4 small screws for battery. Be sure to not lose them. I recommend a PH00 bit for the large screws on the daughter and main boards and a PH1 bit for the small screws on the battery and mainboard.

[[File:Pinebook_Pro_new_keyboard-back-removed.jpg|300px|Remove the back panel]]

''Step 3'': Remove the battery.

Once the battery screws are removed, it should be unplugged from the mainboard and removed. Note that there are two unconnected cables lying around, that should remain unconnected. They are used when the battery is disconnected entirely.

[[File:Pinebook_Pro_new_keyboard-zoom-mainboard.jpg.jpg|300px|Zoom on the mainboard]]
[[File:Pinebook_Pro_new_keyboard-zoom-daughterboard.jpg|300px|Zoom on the daughterboard]]

''Step 4'': Unplug the ribbon cables.

NOTE: you should remove the M.2 adapter board now if you have one installed. See elsewhere in this wiki for instructions on how to install/remove that piece.

There are several ribbon cables. To remove, flip up the tab and gentle pull the ribbon out.

* One cable runs from the mainboard to the daughterboard underneath the battery. Detach from both ends. With the battery removed, detach from keyboard shell, and set aside for the new keyboard shell.
* One cable runs between the touchpad and the mainboard. Detach from both ends, and also set aside.
* One cable runs between the keyboard and the mainboard. This one remains attached to the keyboard and only needs to be detached from the mainboard.
* One cable from the LCD attaches near the lid hinge. It should be just unplugged.

''Step 5'': Detach microphone, speakers, and antenna.

[[File:Pinebook_Pro_microphone_removed.jpg|300px|thumb|right|One of the Pinebook Pro microphones after removal]]

The speakers, microphone, and antenna don't have to be detached from the mainboard, but they need to be detached from the keyboard shell. The microphones are held in place by tape, and the speakers have sticky sides. The speakers are found obviously, but the microphones (two of) can be found between the battery and the hinge area. Each microphone can be carefully pulled/wedged out of its position by a small screwdriver or pick. The antenna, similar to the microphones, is found near the hinge area and to the top left of the battery.

''Step 6'': Remove mainboard and daughterboard.

At this point, the mainboard and daughterboards should be removed. When unscrewed (see Step 2) they should pull out fairly easily. Put them aside (including microphones and speakers if left attached.)

[[File:Pinebook_Pro_new_keyboard-all-boards-removed.jpg|300px|All boards removed]]

''Step 7'': Detach the LCD panel.

Step 2 didn't tell you, there are 6 more screws to remove here, 3 for each of the hinges. I recommend a PH1 bit for these screws. Unscrew these and the LCD panel will be able to be removed. You may have to jiggle or move the hinges for this. When detached, be sure to place the LCD panel such that the display is protected.

[[File:Pinebook_Pro_new_keyboard-detached-display.jpg|300px|Display detached]]
[[File:Pinebook_Pro_new_keyboard-detached-display2.jpg|300px|Display detached (front)]]

''Step 8'': Try not to break your touchpad

'''NOTE This section really feels like you're going to break something.'''

The touchpad is glued to the keyboard shell and it's glued well. There are two places it is glued to. If you can, only the middle must be force-detached. You will think you're going to break it. Gently apply increasing force until the glue begins to detach (you will hear a crackle as it comes off), and continue very slowly until the whole thing is detached. This may take minutes due to that feeling you're going to break it.

I found it helpful to lift the top left plastic bit on the keyboard to unstick that portion of the touchpad, then push on the top left portion of the touchpad to unstick the rest of the touchpad.

[[File:Pinebook_Pro_new_keyboard-touchpad1.jpg|300px|Unmouting the touchpad]]
[[File:Pinebook_Pro_new_keyboard-touchpad2.jpg|300px|Unmouting the touchpad]]
[[File:Pinebook_Pro_new_keyboard-touchpad3.jpg|300px|Unmouting the touchpad]]

''Step 9'': Over the hill, touchpad goes into new shell.

In the new keyboard shell put the touchpad back where it was, hopefully the glue will remain sufficiently attached. If there is a glue issue, this guide unfortunately has no advice currently.

[[File:Pinebook_Pro_new_keyboard-install-touchpad.jpg|300px|Install the touchpad]]

''Step 10'': Reattach the LCD panel.

The LCD panel should slot back into the keyboard frame, the same way it came out. If the hinges were moved, they should be *very* *gently* closed such that the LCD panel and keyboard closed like normal for the remaining steps.

''Step 11'': Tape it out.

Move any tape from the old keyboard shell to the new one. These items protect the mainboard and daughterboard, and keep various wires in their right place. Some are grey and some are black. For tape that holds the speakers, microhones, or their cables in place, do not reattach yet.

''Step 12'': Board install.

Install the mainboard, the daughtboard, and their connecting ribbon cable. Be sure to put the boards in place, 2 large flat screws for the daughterboard, 3 large flat screws and one small screw for the mainboard, before attempting to place the ribbon.

''Step 13'': Microphone, speaker, and antenna install.

Reattach the microphones, antenna, and speakers to their respective areas, making sure that both are properly oriented - the speaker "out" faces up, and the microphone cables as connected must face up (these are opposite directions.)

''Step 14'': Reattach other ribbon cables.

NOTE: this would be a good time to attach/install the M.2 adapter board if that is desired. See elsewhere in this wiki for those instructions.

The LCD panel, keyboard and touchpad ribbon cables should be reattached. Make sure the flap is open, insert the ribbon into the slot (a portion of the cable will disappear), and push the flap down. The cable should not be easy to pull out.

''Step 15'': Reattach the battery, and final re-tape.

The battery should be installed with the 4 screws holding it in place, and the connector attached to the mainboard. Be sure to keep the two other cables remain unconnected. Ensure all wires and other tapes are held in place.

''Step 16'': Reattach the back panel.

Put the back panel back on, and reattach the 10 screws.

''Step 17'': If you changed from ISO to ANSI or from ANSI to ISO, you'll need to update your firmware now. See the links in Step 0 above.

== Touchpad (trackpad) ==
Documentation for the touchpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]]. It is the only component of the Pinebook Pro held in place with strong adhesive tape. Here are some of its features:

* 2 actuating buttons.

* multi-touch functionality.

* A matte finish that your finger can slide along easily.

* A reasonable size (96mm × 64mm; diagonal: 115.378mm or 4.542”).

=== Troubleshooting ===

If you are having trouble using 2 fingers to scroll or emulate the click of a mouse's right-button, then try these solutions:

* Update the firmware.

* Keep your 2 fingers spread apart rather than close together.

* Individual programs might need to be configured specially.

:* For smooth scrolling and gestures under X-Windows, ''Firefox'' should be launched with with the following environment variable assignment:

::: <code>MOZ_USE_XINPUT2=1</code>

* Experiment with other settings, via [[#X-Windows Configuration|X-Windows Configuration]] or some other system preferences. For example, you could disable double-finger scrolling, and instead enable scrolling by sliding one finger along the edge of the touchpad.

=== Firmware ===
The touchpad controller is connected to the keyboard controller. All touchpad events go through the keyboard controller and its software, then to the keyboard controller's USB port. Note that the touchpad does have separate firmware (which has to be written through the keyboard controller). The touchpad vendor's firmware binary can be flashed from userspace using the following open source command-line utility:

* Kamil Trzciński's [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater pinebook-pro-keyboard-updater].

Naturally, forks have begun to appear:

* Jack Humbert's [https://github.com/jackhumbert/pinebook-pro-keyboard-updater fork]

* Dragan Simic's [https://github.com/dragan-simic/pinebook-pro-keyboard-updater fork]. This one has recently delivered a much improved firmware from the vendor one, which greatly improves the control of the cursor (see this [https://forum.pine64.org/showthread.php?tid=14531 thread] for discussion). Before installing this update, consider resetting to the defaults any configuration of your touchpad.

'''All Pinebook Pros shipped from the factory have the old buggy version installed so consider updating the keyboard and touchpad firmware with the latest fixes from Dragan.'''

{{warning| DO NOT update the touchpad firmware before checking which keyboard IC your Pinebook Pro has. Some Pinebook Pro were delivered with a ''SH61F83'' instead of a ''SH68F83''. The SH61F83 can only be written 8 times, this will render the keyboard and touchpad unusable if this limit is reached when step 1 (see below) is flashed. See [https://reddit.com/r/PINE64official/comments/loq4db/very_disappointed/ Reddit SH61F83 thread]. The keyboard IC corresponds to ''U23'' on the [[#Pinebook_Pro_Schematics_and_Certifications|top layer silkscreen of the main board]]. It is located under the keyboard flat flexible cable. All the PBPs from the post-pandemic batches have ''SH61F83'' but TL Lim claimed they can be flashed just the same. No updated datasheet or a statement from the MCU vendor was provided though, so proceed at your own risk. Experience shows flashing those works for at least one time.}}

Before updating ''any'' firmware, your Pinebook Pro should be either fully charged or, preferably, running from mains. This utility will be writing data to chips on the keyboard and touchpad, so a loss of power during any stage of the update can result in irrecoverable damage to your touchpad or keyboard.

The scripts ought to work on all operating systems available for the Pinebook Pro. Some operating systems may however, require installation of relevant dependencies. The instructions below assume a Debian desktop. To install these dependencies, newer Pinebook Pro models that come with Manjaro will require a different command.

There are two keyboard versions of the Pinebook Pro: ISO (vertical Enter key) and ANSI (horizontal Enter key). You need to know which model you have prior to running the updater.
Firmware update steps for both models are listed below.

What you will need:

* Connection to internet for getting dependencies, either through WiFi or wired ethernet (USB dongle).
* Your Pinebook Pro fully charged or running from mains power.
* An external USB keyboard and mouse (or access to the Pinebook Pro via SSH. Please note that for some configurations, the SSH service might not be available without first having logged in once. In this case, you will definitely want at least an external keyboard or UART serial console).

==== ISO Model ====

From the terminal command line:

(Debian distros)

git clone https://github.com/dragan-simic/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make

(Arch distros: eg Manjaro -- NOTE:[https://www.garron.me/en/bits/build-essential-arch-linux.html build-essential], [https://aur.archlinux.org/packages/xxd-standalone xxd] are named differently. Arch linux [https://bbs.archlinux.org/viewtopic.php?id=44950 does not split its packages] as foo and foo-dev)

git clone https://github.com/dragan-simic/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo pacman -Syu base-devel xxd-standalone libusb
make

The next steps are identical for both Debian and Arch distros.

Step 1

cd pinebook-pro-keyboard-updater
sudo ./updater step-1
sudo poweroff # do not use 'reboot'

Step 2 (after booting)

cd pinebook-pro-keyboard-updater
sudo ./updater step-2 iso
sudo poweroff # do not use 'reboot'

==== ANSI Model ====

{{Hint| Note: Running step 1 on the ANSI keyboard model will make the keyboard and touchpad inaccessible until step 2 is run, so an external keyboard must be connected to complete the update on this model!}}

From the terminal command line:

(Debian distros)

git clone https://github.com/dragan-simic/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make

(Arch distros: eg Manjaro -- NOTE:[https://www.garron.me/en/bits/build-essential-arch-linux.html build-essential], [https://aur.archlinux.org/packages/xxd-standalone xxd] are named differently. Arch linux [https://bbs.archlinux.org/viewtopic.php?id=44950 does not split its packages] as foo and foo-dev)

git clone https://github.com/dragan-simic/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo pacman -Syu base-devel xxd-standalone libusb
make

The next steps are identical for both Debian and Arch distros.

Step 1

cd pinebook-pro-keyboard-updater
sudo ./updater step-1
sudo poweroff # do not use 'reboot'

Step 2 (after booting)

cd pinebook-pro-keyboard-updater
sudo ./updater step-2 ansi
sudo poweroff # do not use 'reboot'

When done, if some of the keys produce incorrect characters, please check your OS’s language settings. For ANSI users, the default OS may have shipped with English UK as the default language. You can change it to English US if desired.

==== Revised Firmware ====

In addition, you might consider using revised firmware data. This is one final step that should not require a reboot:

Step 3: '''ISO''' (after booting)

sudo ./updater flash-kb firmware/default_iso.hex

Step 3: '''ANSI''' (after booting)

sudo ./updater flash-kb firmware/default_ansi.hex

=== X Window System Configuration ===

{{Info|Before making adjustments, consider updating the firmware. Reset your adjustments before updating the firmware, so that your adjustments do not interfere with new functionality.}}

When using X.Org display server the touchpad can be handled either by ''libinput'' or ''synaptic'' input drivers. The former allows to have shared configuration for both X.Org and Wayland but the latter provides more tunables (e.g. configurable edge scrolling, circular scrolling, mapping of multi-touch events to mouse buttons etc.)

Some forum members have found that an adjustment to X11 will allow finer motion in the touchpad. If you use the ''synaptic'' mouse/touchpad driver, use this command to make the change live:

synclient MinSpeed=0.2

You may experiment with different settings, but 0.25 was tested as helping noticeably.

To make the change persist across reboots, change the file '''/etc/X11/xorg.conf''' similar to below:

Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
'''Option "MinSpeed" "0.25"'''
EndSection

The line "Option "MinSpeed" "0.25"" is changed here.

Another forum user built on the above settings a little, and have found these to be very good:

synclient MinSpeed=0.25
synclient TapButton1=1
synclient TapButton2=3
synclient TapButton3=2
synclient FingerLow=30
synclient PalmDetect=1
synclient VertScrollDelta=64
synclient HorizScrollDelta=64

''FingerLow'' has the same value as 'FingerHigh' in one config (30). It is believed to help reduce mouse movement as you lift your finger, but it's unknown whether synaptic works like this.
You may find this config to be comfortable for daily use.

''TabButton'' allows to just tab the touchpad instead of physically pressing it down (to get this click noise).

The right mouse click is emulated by tapping with two fingers on the touchpad. If you feel that this is not very responsive you can try this value:

synclient MaxTapTime=250

Some users may encounter an issue with the mouse jumping when typing when using libinput driver due to their hand hitting the touchpad which can be fixed by updating the X.Org settings to disable it while typing. One can disable the touchpad while typing by setting the below option in the X.Org config simliar to the previous example.

Option "DisableWhileTyping" "on"

The setting can be verified by using the xinput command to first list the devices and then listing the properties for the touchpad device. Exact commands to check this have been omitted for save of brevity. If DisableWhileTyping is shown enabled but does not appear to be working the issue may be due to the fact that the keyboard is connected to a USB bus which causes it to be seen as a external keyboard. Make sure you have libinput version 1.19.0 or later installed as it includes the necessary quirk.

Synaptic driver users can add ''syndaemon'' to their X11 session for the same effect.

== Power Supply ==
* Input Power: 5 V DC, 15 W (current limit 3 A, see also inside photos of the factory-provided DC adapter: [[:File:Pbp_charger_top.jpg|top]], [[:File:Pbp_charger_bottom.jpg|bottom]])
* Mechanical: 3.5 mm OD / 1.35 mm ID, barrel jack (also known as DC 35135 socket)
* USB-C 5 V, 12.5 W (current limit is at 2.5 A regardless of the USB PD negotiations result)
* Only use one power input at a time, barrel jack '''or''' USB-C (note: some powerful Type-C adapters have rather limited current for 5 V operation, and e.g. 2 A won't be enough to run the system and charge the battery at the same time, so check the specs)

[[Pinebook Pro power and charging]] explains how exactly external power supply is used to run the system and charge the battery, as there are several counter-intuitive details about the process.

== LEDs ==
In total, there are four LEDs on the Pinebook Pro, three of which are placed in the top-left side of the keyboard, and one near the barrel port:

# The red LED next to the barrel port indicates charging, in three ways. First, it will illuminate steadily when either the barrel jack power supply or a USB Type-C charger is connected to the Pinebook Pro, and the charging is active (that means power is supplied to the battery and system in parallel, and if it's not enough the battery can still be discharging). Second, if the battery is at 100 %, the LED will remain turned off regardless of the connected power input (however, this is not possible for more than a split-second when the system is running). Third, this LED will flash at 0.5 Hz if there are any problems that prevent charging, such as the [[Pinebook_Pro_power_and_charging#Battery_temperature_fix|battery becoming too hot]]. To fully understand all the nuances, read the [[Pinebook_Pro_power_and_charging#Charging_indicator_LED|corresponding article]].
# The power indicator LED, above the keyboard, supports three different colors: green, amber and red. It is also capable of flashing to indicate eMMC activity, with proper software support. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).
# The green NumLock LED, above the keyboard.
# The green CapsLock LED, above the keyboard.

The NumLock and CapsLock LEDs serve their usual purposes on a keyboard, but they also have a secondary function. When the privacy switches get activated they blink to confirm that the switch has been activated.

== Webcam ==
{{Hint| You can use Cheese to test the Camera functionality}}
* Streaming video resolutions supported, (uncompressed):
** 320 x 240
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Still frame resolutions supported:
** 160 x 120
** 176 x 144
** 320 x 240
** 352 x 288
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200

== Audio ==
=== ALSA configuration ===
If you do not have the integrated sound card selected as the default, create <code>/etc/asound.conf</code> with the following contents:

<pre>
defaults.pcm.!card rockchipes8316c
defaults.ctl.!card rockchipes8316c
</pre>

If you want to enable software mixing (dmix) by default for all ALSA apps (works without Pipewire or PulseAudio), make <code>/usr/share/alsa/cards/simple-card.conf</code> file contain this:

<pre>
# default with dmix/dsnoop
simple-card.pcm.default {
@args [ CARD ]
@args.CARD {
type string
}
type asym
playback.pcm {
type plug
slave.pcm {
@func concat
strings [ "dmix:CARD=" $CARD ",RATE=44100" ]
}
}
capture.pcm {
type plug
slave.pcm {
@func concat
strings [ "dsnoop:CARD=" $CARD ",RATE=44100" ]
}
}
}
</pre>

=== Pop/click suppression workaround ===

If you're annoyed by loud popping and clicking sounds, which occur a few seconds after the sound playback stops as a result of the components of the audio chain being turned on and off automatically by the Linux kernel, you can execute the following command manually, or automatically on boot using the <code>tmpfiles.d</code> systemd feature, for example:

: <code>echo 50 > /sys/kernel/debug/asoc/rockchip,es8316-codec/dapm_pop_time</code>

This is a workaround because it effectively (ab)uses a built-in debugging feature of the Linux kernel's audio subsystem, and one of the downsides is that a lot of messages are produced in the kernel log whenever the components of the audio chain are turned on and off automatically by the kernel.

=== Speaker polarity workaround ===
On newer Pinebook Pro batches, the inverted built-in speaker polarity issue has been fixed. On these units, the speaker polarity can be made reversed again by the <code>alsa-ucm-conf</code> package, which configures ALSA devices continuously. One workaround would be to remove the package, and the speaker polarity will no longer be set incorrectly. However, this also prevents the built-in speakers from being muted when an output device is plugged into the aux port.

Another workaround is to edit file <code>/usr/share/alsa/ucm2/Rockchip/es8316/HiFi.conf</code> and change all instances of <code>R Invert</code> to <code>Normal</code>. This is a workaround because it's likely to be overwritten and lost if the <code>alsa-ucm-conf</code> package is updated.

== Microphones ==
While it has been said that some Pinebook Pro units contain only one microphone despite having two labeled microphone holes on the outer casing, other units do indeed contain two microphones. It is presently unclear which batches have either configuration. Units from the initial community batch of 1000 units (following the initial 100) are believed to contain two, populating both labeled holes.

The wires leading to both microphones connect to the mainboard with a small white plastic connector, located directly adjacent to the ribbon cable attachment point for the keyboard interface.

=== Built-in microphones not working ===
If pavucontrol input doesn't show microphone activity try changing the [[Pinebook_Pro#Privacy_Switches|privacy switches]]. If the switches are in the correct place and microphone input isn't working you can run <code>alsamixer</code> from the command line, hit F6 and select the <code>es8316</code>, hit F4 to get to the capture screen, select the bar labeled ADC, increase the gain to 0 dB, change the audio profile in pavucontrol to another one with input. Additionally you may want to modify ADC PGA to get the levels to where you want them. If that still hasn't fixed it you may want to check that the microphone connector is plugged in (see the section [[#Technical Reference|Technical Reference]]).

=== External wired microphone not working ===
If you connect a headset with a microphone, you might need to open <code>alsamixer</code>, change card to <code>es8316</code>, and change option <code>Differential Mux</code> from <code>lin1-rin1</code> to <code>lin2-rin2</code>.

== Bluetooth and WiFi ==
[[File:PinebookPro_WirelessIC_Location.jpg|400px|thumb|right|The Pinebook Pro's AP6256 wireless module]]

===Hardware Overview===
The Pinebook Pro contains an AMPAK AP6256 wireless module to provide Wi-Fi (compliant to IEEE 802.11ac) and Bluetooth (compliant to Bluetooth SIG revision 5.0). The module contains a Broadcom transceiver IC, believed to be the BCM43456, as well as the support electronics needed to allow the Wi-Fi and Bluetooth modes to share a single antenna.

The wireless module interfaces with the Pinebook Pro’s system-on-chip using a combination of three interfaces: Bluetooth functionality is operated by serial UART and PCM, while the Wi-Fi component uses SDIO. It is unknown if the module’s Bluetooth capabilities are usable under operating systems that do not support SDIO.

The module’s RF antenna pin is exposed on the mainboard via a standard Hirose U.FL connector, where a coaxial feedline links it to a flexible adhesive antenna situated near the upper right corner of the Pinebook Pro’s battery. As the RF connector is fragile and easily damaged, it should be handled carefully during connection and disconnection, and should not be reconnected frequently.

===Issues===
Problems have been reported with the Wi-Fi transceiver’s reliability during extended periods of high throughput, especially on the 2.4 GHz band. While the cause of this has yet to be determined, switching to the 5 GHz band may improve stability.

Since the Bluetooth transceiver shares both its spectrum and antenna with 2.4 GHz Wi-Fi, simultaneous use of these modes may cause interference, especially when listening to audio over Bluetooth. If Bluetooth audio cuts out frequently, switching to the 5 GHz band – or deactivating Wi-Fi – may help.

===Wi-Fi Capabilities===
Wi-Fi on the Pinebook Pro is capable of reaching a maximum data transfer rate of approximately 433 megabits per second, using one spatial stream. The transceiver does not support multiple spatial streams or 160-MHz channel bandwidths.

The Wi-Fi transceiver supports the lower thirteen standard channels on the 2.4 GHz band, using a bandwidth of 20 MHz. At least twenty-four channels are supported on the 5 GHz band, spanning frequencies from 5180 to 5320 MHz, 5500 to 5720 MHz, and 5745 to 5825 MHz, with bandwidths of 20, 40, or 80 MHz. This might vary depending on the country you specify in the wireless settings, see ''iw reg get; iw list''.

Maximum reception sensitivity for both bands is approximately -92 dBm. The receiver can tolerate input intensities of no more than -20 dBm on the 2.4 GHz band, and no more than -30 dBm on the 5 GHz band. Maximum transmission power is approximately +15 dBm for either band, falling further to approximately +10 dBm at higher data transfer rates on the 5 GHz band.

With current available drivers and firmware, the Wi-Fi interface supports infrastructure, ad-hoc, and access-point modes with satisfactory reliability. Monitor mode is not presently supported. Wi-Fi Direct features may be available, but it is unclear how to make use of them under Linux.

Be aware that Linux userspace utilities, such as <code>iw</code>, may report inaccurate information about the capabilities of wireless devices. Parameter values derived from vendor datasheets, or direct testing, should be preferred to the outputs of hardware-querying tools. That said, if a certain feature is not reported by ''iw'' it means the currently running kernel driver plus firmware combination doesn't support it, even when the hardware is capable.

WPA3 PSK support should be possible with ''iwd'' but not ''wpa_supplicant'', see [https://github.com/raspberrypi/linux/issues/4718#issuecomment-1279951709 this ticket] for details.

===Bluetooth Capabilities===
Bluetooth data transfer speeds have an indicated maximum of 3 megabits per second, but it is unclear what practical data rates can be expected. Audio streaming over Bluetooth is functioning normally, as is networking. Bluetooth Low-Energy functions, such as interacting with Bluetooth beacons, have not yet been tested conclusively.

The Bluetooth transceiver supports all 79 channel allocations, spanning frequencies from 2402 MHz to 2480 MHz. Reception sensitivity is approximately -85 dBm, with a maximum tolerable reception intensity of -20 dBm. Bluetooth transmission power is limited to +10 dBm.

===Disabling Bluetooth===

To disable Bluetooth under Linux once:

sudo rfkill block bluetooth

To confirm if Bluetooth under Linux is disabled:

rfkill

To disable Bluetooth on boot (note: for distributions such as Manjaro XFCE see the step below):

sudo systemctl enable rfkill-block@bluetooth

To disable Bluetooth on certain distributions, such as Manjaro XFCE, right click on the Bluetooth panel icon, select plugins, then PowerManager, then configuration and then deselect the auto power on option

== LCD Panel ==
* Model: BOE NV140FHM-N49
* 14.0" (35.56 cm) diagonal size
* 1920x1080 resolution
* 60 Hz refresh rate
* IPS technology
* 1000:1 contrast
* 250 nit brightness
* 63% sRGB coverage
* 6-bit color
* 30-pin eDP connection

== External ports list ==
Here are a list of the external ports. See [[Pinebook_Pro#Expansion_Ports|Technical Reference - Expansion Ports]] for port specifications.
* Left side
** Barrel jack for power, (with LED)
** USB 3, Type A
** USB 3, Type C
* Right side
** USB 2, Type A
** Standard headset jack
** MicroSD card slot

== Using the serial console UART ==
[[File:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter. This shows signals from the Pinebook Pro's point of view, so connect the adapter's RX to ring 1, and TX to the tip. See also the [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pine64 official document] describing this.]]

Serial console UART is enabled by flipping the UART switch to the ON position (item 9). To do so, you need to remove the Pinebook Pro's bottom cover by following the [[Pinebook_Pro#Disassembly_and_Reassembly|disassembly and reassembly guidelines]]. The OFF position is towards the touchpad, while the ON position is towards the display hinges.

With the UART switch in the ON position, the console is relayed via the headset jack, on which the audio output is no longer available. Please ensure that you are using a 3.3 V UART interface (such as the CH340, FTDI-232R, or PL2303, which are available in both 3.3 V and 5 V variants) to avoid damage to the RK3399 SoC. Older version of the serial console cable sold by the Pine Store used wrong voltage level and should not be used, see [https://forum.pine64.org/showthread.php?tid=9367 this forum thread] for further information. Recent version of the same cable uses the right voltage level, which can also be checked by measuring the voltage on the TX ring.

Insert the USB plug of the cable into a USB port on the machine that you will use to monitor the Pinebook Pro's serial console, ensuring that the audio jack of the serial cable is be fully inserted into the Pinebook Pro's headphone port. Run <code>lsusb</code> in a terminal and you should see a line similar to this:

Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

Serial console output should now be accessible on the respective machine using a terminal emulator, such as screen, picocom or minicom. Here are a few examples of how to invoke a terminal emuator:

* <code>screen /dev/ttyUSB0 1500000</code>
* <code>picocom /dev/ttyUSB0 -b 1500000</code>
* <code>minicom -D /dev/ttyUSB0 -b 1500000</code>

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 SSDs that support the NVMe standard (SATA is not supported). The adapter supports '''M''' and '''M'''+'''B''' keyed devices, in both 2242 and 2280 physical sizes, which are the most commonly available. In addition, 2230 and 2260 sizes are also supported, though NVMe devices that use those sizes are rare.

Make sure to read the notes in [[Pinebook Pro Hardware Accessory Compatibility#NVMe SSD drives]] before selecting an M.2 SSD for your Pinebook Pro, because there are certain limitations. Once you have fitted and tested your NVMe drive, please consider adding a note to that page

Please see [[Pinebook Pro Troubleshooting Guide#NVMe SSD issues|a separate section]] that describes reported issues with the NVMe drives in Pinebook Pro.

=== Installing the adapter ===
The V2.1-2019-0809 SSD adapter that shipped with the initial Pinebook Pro batches had significant issues. A repair kit will be shipped to address those issues.
(If necessary, it can be modified to work. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing these modifications.)

The updated SSD adapter, labeled V2-2019-1107, takes into account the prior problems with touchpad interference. New orders as of Feb. 22nd, 2020 will be the updated adapter.

This is the link to the Pinebook Pro accessories in the store: https://pine64.com/?v=0446c16e2e66

Actual installation instructions are a work in progress. Unofficial instructions for installing V2-2019-1107 can be found [https://eli.gladman.cc/blog/2020/06/23/pine-book-pro-nvme.html here].

=== Post NVMe install power limiting ===
{{Warning|Newer versions of the '''nvme-cli''' package have been [https://github.com/linux-nvme/nvme-cli/commit/254ff3d007a11ef5b9513d8906b5f1fe35074a84 changed] to use '''-V''' (uppercase) instead of '''-v''' (lowercase) as the option name for specifying values. Please update the parameter names used in the commands below, if your Linux distribution packages a newer version.}}

Some NVMe SSDs allow reducing the maximum amount of power. Doing so may reduce the speed, but it may be needed in the Pinebook Pro to both improve reliability on battery: Some NVME may be stable with default settings when runnning on AC power but cause frequent kernel panics (system freeze with power LED blinking red/green) when running on battery. Reducing NVME power drain solves this in some cases. And reducing power used gives better battery life.
Here are the commands to obtain and change the power settings. The package 'nvme-cli' is required to run these commands. The example shows how to find the available power states, and then sets it to the lowest, non-standby setting, (which is 3.8 watts for the device shown):

$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
...
ps 0 : mp:9.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.60W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.80W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0450W non-operational enlat:2000 exlat:2000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0040W non-operational enlat:6000 exlat:8000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

$ sudo nvme get-feature /dev/nvme0 -f 2
get-feature:0x2 (Power Management), Current value:00000000
$ sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s
set-feature:02 (Power Management), value:0x000002

Some NVMe SSDs don't appear to allow saving the setting with "-s" option. In those cases, leave off the "-s" and use a startup script to set the non-default power state at boot. If you want to test performance without saving the new power setting semi-permanantly, then leave off the "-s" option.

On systemd based distributions like Manjaro, a non-default power state for an NVME can be set using a systemd service. This is useful in cases where the NVME drive does not save the power state and/or uses APST. An example systemd service, nvme-throttle.service, is shown below:

[Unit]
Description=Throttles NVME to lesss power hungry mode
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[Service]
Type=oneshot
ExecStart=/usr/bin/nvme set-feature /dev/nvme0 -f 2 -v 1

[Install]
WantedBy=multi-user.target suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

Here the value after "-v" is the maximum power state that you want your SSD to use. This will be executed at system startup, and every time your system exits any suspend mode that might reset the SSD to default values.

This file needs to be placed in the /etc/systemd/system directory. Afterwards, to activate the service, run:

systemctl daemon-reload
systemctl enable --now nvme-throttle.service

There is another power saving feature for NVMes, APST, (Autonomous Power State Transitions). This performs the power saving & transitions based on usage. To check if you have a NVMe SSD with this feature:

$ sudo nvme get-feature -f 0x0c -H /dev/nvme0

Information for this feature, (on a Pinebook Pro), is a work in progress. It is enabled by default in latest Manjaro kernels and reported to work.
On some NVME SSDS (WD), APST is compatible with limiting NVME maximum power: APST will work and not exceed maximum power state defined using
previous method.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. It can automatically mount when booting from either the eMMC or an SD card. This applies to Linux, FreeBSD, and Chromium, using the normal partitioning and file system creation tools. Android requires testing.

=== Using as OS root drive ===
The SoC does not include the NVMe boot code, so the NVMe is not in the SoC's boot order. However, using the [https://github.com/mrfixit2001/updates_repo/blob/v1.1/pinebook/filesystem/mrfixit_update.sh U-Boot update script] from the mrfixit2001 Debian or [https://pastebin.com/raw/EeK074XB Arglebargle's modified script], and [https://github.com/pcm720/rockchip-u-boot/releases the modified u-boot images] provided by forum user pcm720, you can now add support to boot from an NVMe drive. Binary images are useable with SD, eMMC, and [[Pinebook_Pro_SPI|SPI flash]]. For OS images using the mainline kernel, there are a few variants of U-Boot available that also support NVMe as the OS drive. Though these may require writing the U-Boot to the SPI flash for proper use of the NVMe as the OS drive.

The current boot order, per last testing, for this modified U-Boot is:
* MicroSD
* eMMC
* NVMe

For more information, please refer to [https://forum.pine64.org/showthread.php?tid=8439&pid=53764#pid53764 the forum post.]

It is also possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Currently, it is necessary to have the U-Boot code on an eMMC or SD card. (A forum member [https://forum.pine64.org/showthread.php?tid=8439 posted here] about using a modified version of U-Boot with NVMe drivers, that uses '''/boot''' and '''/''' off the NVMe drive. So this may change in the future.)

Please see [[Pinebook_Pro#Bootable Storage|Bootable Storage]].

== Caring for the Pinebook Pro ==

=== Bypass Cables ===
{{Warning|'''Do not connect the bypass cables with the battery connected.''' Using the bypass cables with the battery connected can permanently damage your Pinebook Pro. After you're done with using the bypass cables and want to return to the default setup, make sure to affix the bypass cables to the main body of the laptop using adhesive tape, in the same way as it was done in the factory. This ensures that the exposed leads in the connectors on the bypass cables don't touch any conductive surface inside the laptop, which may cause a short.}}

The mainboard features two bypass cables that are to be used only with the battery disconnected. The two bypass cables are disconnected by default. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run your Pinebook Pro with no battery. Please refer to this [https://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice] for more details.

Connecting the bypass cables together effectively connects the charger input where the battery output is, which also bypasses the charging circuit inside the Pinebook Pro. Thus, with the bypass cables connected together, the charger powers the Pinebook Pro directly, just like the battery does it when the laptop is running on battery power. This also means that no input current limiting is any longer in place, making it possible to draw more than 3 A from the charger, and to trigger its overcurrent protection, which may cause operating system instability and crashes.

Despite the bypass cables having two conductors, they are used as a single conductor. Having both wires soldered together on either side of the bypass cables is normal, and such load-sharing design allows use of a compact connector on the bypass cables.

When removing the large RF shield found on the mainboard, for example when shorting the pins on the SPI chip, make absolutely sure to align it correctly while putting it back. Failing to do so can result in shorting the battery to the ground, due to the close proximity of the solder pads for the bypass cables, which would prevent the normal operation and effectively cause a fire hazard. It is highly recommended to disconnect the battery before removing the RF shield, and before putting it back.

=== Self-Service Step-by-Step Guides ===
These are self-service instruction guides for the disassembly of the 14-inch Pinebook, but they still almost directly apply to the Pinebook Pro:

* [http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Battery_Removal_Guide.pdf Lithium Battery Pack Removal Guide]
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_14-Screen_Removal_Guide.pdf LCD Panel Screen Removal Guide]
* [http://files.pine64.org/doc/pinebook/guide/Pinebook_14-eMMC_Removal_Guide.pdf eMMC Module Removal Removal Guide]

Assembling it back requires the described steps to be performed in the reverse order.

== Using the SPI flash device ==
{{Warning|'''When removing the large RF shield found on the mainboard, to be able to short the pins on the SPI chip, make absolutely sure to align it correctly while putting it back.''' Failing to do so can result in shorting the battery to the ground, due to the close proximity of the solder pads for the bypass cables, which would prevent the normal operation and effectively cause a fire hazard. It is highly recommended to disconnect the battery before removing the RF shield, and before putting it back.}}

See [[Pinebook Pro SPI]] for details.

The Pinebook Pro comes with a 128Mbit, (16MByte), flash device suitable for initial boot target, to store the bootloader. The SoC used on the Pinebook Pro boots from this SPI flash device first, before eMMC or SD card. At present, April 19, 2020, the Pinebook Pros ship without anything programmed in the SPI flash device. So the SoC moves on to the next potential boot device, the eMMC. ARM/ARM64 computers do not have a standardized BIOS, yet.

Here is some information on using the SPI flash device:

* You need the kernel built with SPI flash device support, which will supply a device similar to: '''/dev/mtd0'''
* The Linux package below, will need to be available: ''mtd-utils''
* You can then use this program from the package to write the SPI device: <code>flashcp <filename> /dev/mtd0</code>

Even if you need to recover from a defective bootloader written to the SPI flash, you can simply short pin 6 of the SPI flash to GND and boot. This will render the SoC bootrom unable to read from the SPI flash and have it fall back to reading the bootloader from other boot media like the eMMC or Micro SD card.

The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware. At present, April 19th, 2020, there is no good bootloader image to flash into the SPI flash device. This is expected to change, as there are people working on issue.

== Software tuning guide ==

The software tuning guides can be found in the article [[Pinebook Pro Software Tuning Guide]].

== Troubleshooting guide ==

Do not panic if something goes wrong or in an unexpected way. Instead, stop and consider carefully how to undo something, or how to redo it. This particularly applies when flashing a new operating system, or flashing new firmware to the keyboard or touchpad. If everything fails, consider reporting the issue on the forums, with as many relevant details as available.

Please, have a look at the [[Pinebook Pro Troubleshooting Guide]], which details a number of issues you may encounter.

== Hardware/Accessory Compatibility ==
Please contribute to the [[Pinebook Pro Hardware Accessory Compatibility|hardware/accessory compatibility page]], which lists the status of hardware tested with the Pinebook Pro. Available hardware categories include the following:

* [[Pinebook Pro Hardware Accessory Compatibility#NVMe SSD drives|NVMe SSD drives]]
* [[Pinebook Pro Hardware Accessory Compatibility#USB hardware|USB hardware]]
* [[Pinebook Pro Hardware Accessory Compatibility#USB C alternate mode DP|USB-C alternate mode DP]]
* [[Pinebook Pro Hardware Accessory Compatibility#Other hardware|Other hardware]]

== Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

[[File:Hinges_cover_removed_1.jpeg|300px|thumb|right|Hinge area of the Pinebook Pro lid with the cover removed]]
[[File:Hinges_cover_removed_2.jpeg|300px|thumb|right|Close-up of a Pinebook Pro lid hinge]]

There are a few '''mandatory''' precautions to be taken:

* Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.
* When removing the back cover plate, *do not, under any circumstances, slide your fingertips between the metal shell and the plastic frame!* The back cover plate edges are sharp, and when combined with the pressure and movement generated from, specifically, attempting to slide the tips of your fingers along the bottom edge of the plate along the lid-hinge, they *will* slice open the tips of your fingers like a knife.
* When removing the back cover plate, use care to avoid damaging the speakers. They can be stuck to the back cover with double-sided tape, and the thin wires are very delicate. Newer Pinebook Pro laptops (as of the May 2021 batch, and perhaps earlier) seem to lack the double-sided tape to the rear cover, instead opting for tape or glue that makes them stick to the front cover. Nevertheless, be gentle when removing the back cover.

[[File:PinebookProScrewGuide.png|400px|thumb|right|Pinebook Pro external screws (this particular unit has suffered damage on screw (4)L)]]

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. There are four (4) short screws along the front edge, and six (6) long screws along the 3 remaining sides. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis. The aluminum case is held on only by screws. There are no plastic snaps, and the shell should pull away without any effort. If you experience any resistance at all stop and ensure all ten (10) screws are accounted for.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. Before replacing the aluminum back-plate, ensure that the speakers are properly seated by pressing gently on the hard plastic edge of the speaker module. Slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the touchpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 4 short screws.

The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side (which may be caused by the aforementioned misseating of the speakers), open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, re-open the machine and check for misseated components.

A basic 3D model to print replacement standoffs for the back cover screws is [https://www.thingiverse.com/thing:4226648 available on Thingiverse], until the official drawings or 3D models are made available.

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).

=== Display Disassembly===
It is not recommended to adjust the position of the lid when the bottom cover is removed, because the bottom cover provides structural strength, so the lid should be open fully as the first step, before starting any disassembly of the laptop. After opening the lid, remove the bottom cover by following the instruction found in the section above. Alternatively, you can keep the lid closed and remove the screws that hold the hinges to the main laptop body, as described in [[#Caring for the PineBook Pro|Pinebook Service Step by Step Guides]].

Parts of the hinge mechanism, as well as the screws that hold the hinges to the lid, are hidden behind an elongated plastic U-shaped cover that snaps in place using latches. Use a dedicated plastic prying tool or a guitar pick to gently pry the cover and remove it, starting from the outer edge. Once you pry the cover to a certain extent, it should be possible to remove it fully using only your hands. The U-shaped cover is rather sturdy, but still be careful not to break or bend it.

There are two small screws hidden underneath the two small rubber nubs on the upper part of the screen bezel, so first gently remove the nubs and then remove the screws. The screen bezel is held in place with a combination of latches and some adhesive tape, which is there to prevent dust ingress. The adhesive isn't very strong, and the bezel is capable of flexing back into shape after being twisted to a certain extent. There is more adhesive on the bottom part of the screen bezel, so be more careful while prying that section apart. Use the same prying tool that you used for the U-shaped cover, and work it around the outer edges of the screen bezel.

== Internal Layout ==

=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory module (26; Note: Some datasheets indicate a low supported number of mating cycles.)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC module (24), and enabling serial console UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode. This mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg|500px]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe x4 slot for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Touchpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - enables serial console UART via headphone jack
|-
! scope=row | 10
| Socket || Power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Touchpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || MicroSD card slot
|-
! scope=row | 16
| Socket || Headphone / serial console UART jack
|-
! scope=row | 17
| Socket || USB 2.0 Type A
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0 Type A
|-
! scope=row | 33
| Socket || USB 3.0 Type C
|}

=== Smallboard detailed picture ===

[[File:Pinebook_pro_smallboard.jpg|600px]]

== Bootable Storage ==

[[File:Pbp_emmc_disable_sw.jpg|480px|thumb|The PineBook Pro eMMC module and switch, shown in 'enabled' position]]

=== Boot sequence details ===
The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768, (sector 64 if using 512 byte sectors). This is where U-Boot code would reside on any media that is bootable, [[RK3399_boot_sequence|RK3399 boot sequence]]

=== Boot devices ===

The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Manjaro + KDE build with [https://www.denx.de/wiki/U-Boot/ u-boot] on the eMMC. Its boot order is: SD, USB, then eMMC.

(An update has been pushed for the older Debian + MATE build that improves compatibility with booting other operating systems from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===

The eMMC appears to be hot-pluggable. This can be useful if trying to recover data or a broken install. Best practice is probably to turn the eMMC switch to off position before changing modules. Note that the enable/disable label on the silkscreen is incorrect on some board revisions (known bad on v2.1).

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition, may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

If the eMMC module is enabled after boot from an SD card, you can detect this change with the following commands as user "root":

echo fe330000.mmc >/sys/bus/platform/drivers/sdhci-arasan/unbind
echo fe330000.mmc >/sys/bus/platform/drivers/sdhci-arasan/bind

(Note: with the device trees coming with older kernels (Linux < 5.11), the device name may be fe330000.sdhci instead of fe330000.mmc)

== Case Dimensions and Data ==
* Dimensions: 329 mm x 220 mm x 12 mm (W x D x H)
* Weight: 1.26 kg
* Screws on the bottom lid
** Philips-head type screws
** M2 flat-head machine screws
** 4 x short screw (used along the front edge): head diameter - 3.44 mm, thread diameter - 1.97 mm, thread length - 2.1 mm, overall length - 3.05 mm
** 6 x long screw (used elsewhere): head diameter - 3.44 mm, thread diameter - 1.97 mm, thread length - 4.41 mm, overall length - 5.85 mm
* Rubber feet
** 18 mm diameter
** 3 mm height
** Dome shaped

== SoC and Memory Specification ==
[[File:Rockchip_RK3399.png|right]]
* Based on Rockchip RK3399

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* Graphic interface standards:
** OpenGL® ES 1.1, 1.2, 2.0, 3.0, 3.1, 3.2. (Panfrost has initial support of 3.0 beginning 2020/02/27)
** Vulkan 1.0, using the Mali binary blob. (Panfrost does not support Vulkan as of 2020/06/24)
** OpenCL™ 1.1, 1.2
** DirectX® 11 FL11_1
** RenderScript™

=== System Memory ===
* RAM Memory:
** LPDDR4
** 800MHz, (limited by RK3399)
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to an 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)
** eMMC version 5.1, HS400, 8 bit on RK3399 side
** Bootable
* SPI flash:
** [[Pinebook Pro SPI]]
** 128Mbit / 16MByte
** 1 bit interface
** Bootable, (first boot device, ahead of eMMC & SD card)
** U-Boot images can be made to work, but as of 2020/06/24 there is no standardized image available.

=== Video out ===
* USB-C Alt mode DP
* Up to 3840x2160 p60, dependant on adapter, (2 lanes verses 4 lanes)

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 512GB tested. SDXC standard says 2TB is the maximum.
** Version SD3.0, (MMC 4.5), up to 50MB/s
** SD card Application Performance Class 1 (A1), (or better), recommended by some users, for better IOPS
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
** Note that high power USB devices may not work reliably on a PBP. Or they may draw enough power to drain the battery even when the PBP is plugged into A.C. One alternative is externally powered USB devices.
* Headphone jack switchable to UART serial console mux circuit

== Additional hardware ==
Hardware that is not part of the SoC.

=== Battery ===
* Lithium Polymer Battery (10,000 mAh; 9,600 mAh in later batches)
* Monitored by CW2015 which only measures the current voltage; reported state (charging/discharging), capacity (State-Of-Charge), remaining runtime and current are (poor) estimates

=== Display ===
* 14.0" 1920x1080 IPS LCD panel
=== Lid closed magnet ===
There is a magnet to detect when the laptop lid is closed, so action can be taken like sleep. This meets up with the Hall sensor on the daughter / small board to detect lid closed.
* The magnet is located on the LCD panel right side, around 1.5 inches up measure from bottom edge.

=== Webcam ===
* Internal USB attached Webcam

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Built-in microphone
* Built-in stereo speakers:
** Oval in design
** 3 mm high x 20 mm x 30 mm

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Optional NVMe adapter ===
* PCIe 1.1, 2.5 GT/s per lane
** Note that due to errata, PCIe is limited to Gen1. See [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/rockchip/rk3399.dtsi?id=712fa1777207c2f2703a6eb618a9699099cbe37b this commit].
* Four PCIe lanes, which can not be bifurcated, but can be used with one- or two-lane NVMe cards
* '''M''' keyed, though '''M'''+'''B''' keyed devices will work too
* Maximum length for M.2 card is 80mm (M.2 2280). The following sizes will also work: 2230, 2242, 2260
* Power: 2.5 W (continuous)
* Does not support SATA M.2 cards
* Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
Pinebook Pro Main Board Schematic And Silkscreen:
* [https://files.pine64.org/doc/PinebookPro/pinebookpro_schematic_v21a_20220419.pdf Pinebook Pro Main Board ver 2.1a Schematic 20220419]
* [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic 20190905]
* [[file:Pinebookpro-v2.1-top-ref.pdf|Pinebook Pro ver 2.1 Top Layer Silkscreen]]
* [[file:Pinebookpro-v2.1-bottom-ref.pdf|Pinebook Pro ver 2.1 Bottom Layer Silkscreen]]

Pinebook Pro Daughter Board Schematic:
* [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]

Optional Pinebook Pro NVMe Adapter Schematic:
* [https://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]

Serial Console Earphone Jack Pinout:
* [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinebook Serial Console Earphone Jack Pinout]

Pinebook Pro Case:
* [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.pdf AutoCAD PDF File ]
* [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.ai AutoCAD AI File ]
* [https://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.dwg AutoCAD DWG File ]

Pinebook Pro Certifications:
* [https://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]
* [https://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]

== Datasheets for Components and Peripherals ==
Rockchip RK3399 SoC information:
* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet v2.1]
* [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.4%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.4, part 1]
* [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part1.pdf Rockchip RK3399 Technical Reference Manual v1.3, part 1] and [https://www.rockchip.fr/Rockchip%20RK3399%20TRM%20V1.3%20Part2.pdf part 2]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet v0.8]

LPDDR4 SDRAM (366-pin BGA):
* [https://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]

eMMC information:
* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [[file:Ds-00220-gd25q127c-rev1-df2f4.pdf|GigaDevice 128Mb SPI Flash Datasheet (updated)]]

Wireless and Bluetooth information:
* [https://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]

Audio codec:
* [http://www.everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec Datasheet]
* [https://forum.pine64.org/attachment.php?aid=1935 Everest ES8316 User Guide with register-level description]

LCD panel:
* [https://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]

USB-related information:
* Internal USB 2.0 hub: [[File:GL850G_USB_Hub_1.07.pdf|GL850G USB Hub Datasheet]]
* USB Type-C Controller: [https://www.onsemi.com/pub/Collateral/FUSB302-D.PDF ON Semiconductor FUSB302 Datasheet]

Touchpad information:
* [https://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf PineBook Pro Touchpad Specification]

Keyboard information:
* [[file:SH68F83V2.0.pdf|Sinowealth SH68F83 Datasheet]]
* US ANSI: XK-HS002 MB27716023

Full HD camera sensor:
* [https://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification (in Chinese)]
* [https://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Datasheet]

Battery-related information:
* Battery charging IC: [https://www.ti.com/lit/ds/symlink/bq24171.pdf?ts=1607068456825&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FBQ24171 Texas Instruments BQ24171 Datasheet]
* Battery monitoring IC: [https://cdn.datasheetspdf.com/pdf-down/C/W/2/CW2015-Cellwise.pdf Cellwise CW2015 Datasheet]
* [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000 mAh Lithium Battery Specification]
* [https://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%209600mAh%20Lithium%20Battery%20Specification.pdf 9600 mAh / 36.48 Wh model WYC40110175P Lithium Battery Specification], used in later batches

Power path device:
* [[file:Sis412dn.pdf|N-MOS / MOSFET]]

NVMe adapter:
* [[file:Hirose-FH26W-35S-0.3SHW%2860%29-datasheet.pdf|FH26-35S-0.3SHW flat flex connector (compatible, not OEM)]]

== Versions ==
Pinebook Pro v1 and v2 were prototype models that did not make it to the public. The "first batch" (First 100 forum preorders) onward are v2.1. [https://forum.pine64.org/showthread.php?tid=8111]

== Skinning and Case Customization ==
Template files for creating custom skins. Each includes template layers for art placement, and CUT lines:

* [[File:Pbp_template_case_bottom.pdf|Case Lid Template]]
* [[File:Pbp_template_case_lid.pdf|Case Bottom Template]]
* [[File:Pbp_template_case_palmrest.pdf|Case Palmrest Template]]

== Other Resources ==
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]

[[Category:Pinebook Pro]]
[[Category:Rockchip RK3399]]

PineNote

2024-11-01T09:41:10Z

Dsimic: /* State of the software */ Cleaned up a bit

[[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 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 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 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 ==

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-29T08:26:14Z

Dsimic: /* Information, Schematics, and Certifications */ More readable

[[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 ==

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-29T08:24:20Z

Dsimic: /* Information, Schematics, and Certifications */ Clarified the use of EMR pen

[[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 ==

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-29T08:23:09Z

Dsimic: /* Information, Schematics, and Certifications */ Small cleanups

[[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 ==

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]]

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-29T08:09:25Z

Dsimic: /* Information, Schematics, and Certifications */ Actually, the subsection is redundant

[[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 ==

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] 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.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start 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-29T08:08:44Z

Dsimic: /* PineNote Developer kit version */ Adjusted the wording a bit, to make it clear what applied to the different versions

[[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 versions ===
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] 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.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start 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-29T06:38:47Z

Dsimic: /* PineNote Developer kit version */ Cleaned up a bit and added a link to the QSG

[[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 Pine 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.
* [[:File:Pinenote quick start guide en ger fr pl.pdf|PineNote Quick Start Guide]]

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]]

File:Pinenote quick start guide en ger fr pl.pdf

2024-10-29T06:36:35Z

Dsimic: PineNote Quick Start Guide

== Summary ==
PineNote Quick Start Guide

PineTab2

2024-10-28T20:27:03Z

Dsimic: /* Getting started */ Linked the quick quide PDF

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes the following items:

* The PineTab2
* Short [[:File:Pinetab2 quick start guide en ger fr pl final.pdf|user guide]]
* Power cable
* The UART adapter board

Note that the UART adapter is in the same package as the power cable, in a second compartment, and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.
The external keyboard has 5 connection pins (the golden pins). four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* WiFi/Bluetooth chip BES2600:
** The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]]. There are at least two code releases available, with two respective/non-interchangeable firmware versions. The latest danctnix kernel has a pretty well working wifi driver.
** The BES2600 Bluetooth driver needs to be implemented.
** Hardware bugs - the power and reset circuitry is not properly implemented in the circuitry, so hard reset of the chip (in the theoretical case it freezes) is impossible without power cycling the whole board.
* The camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMMC 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]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

LCD panel:

* [[:File:Boe-technology-th101mb31ig002-28a-datasheet-v10.pdf|BOE TH101MB31IG002-28A datasheet v1.0]]

== Tutorials and Frequently Asked Questions ==

Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

There's also [[:File:PineTab2_display_panel_disassembly_guide.pdf|PineTab2 disassembly guide]]. The disassembly is a very delicate operation, especially around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PineTab2

2024-10-28T20:26:16Z

Dsimic: /* Getting started */ More small cleanups

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes the following items:

* The PineTab2
* Short user guide
* Power cable
* The UART adapter board

Note that the UART adapter is in the same package as the power cable, in a second compartment, and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.
The external keyboard has 5 connection pins (the golden pins). four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* WiFi/Bluetooth chip BES2600:
** The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]]. There are at least two code releases available, with two respective/non-interchangeable firmware versions. The latest danctnix kernel has a pretty well working wifi driver.
** The BES2600 Bluetooth driver needs to be implemented.
** Hardware bugs - the power and reset circuitry is not properly implemented in the circuitry, so hard reset of the chip (in the theoretical case it freezes) is impossible without power cycling the whole board.
* The camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMMC 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]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

LCD panel:

* [[:File:Boe-technology-th101mb31ig002-28a-datasheet-v10.pdf|BOE TH101MB31IG002-28A datasheet v1.0]]

== Tutorials and Frequently Asked Questions ==

Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

There's also [[:File:PineTab2_display_panel_disassembly_guide.pdf|PineTab2 disassembly guide]]. The disassembly is a very delicate operation, especially around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]

PineTab2

2024-10-28T20:25:38Z

Dsimic: /* Getting started */ Cleaned up a bit

[[File:PineTab2 Front.jpg|250px|thumb|right|The PineTab2 with the detachable keyboard attached]]

The '''PineTab2''' is PINE64's successor to the original [[PineTab]] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover.

The tablet is designed around the Rockchip RK3566 processor, which features 4 energy-efficient Cortex-A55 64-bit ARM cores and enjoys good mainline Linux support. A similarly packaged RISC-V tablet is the [[PineTab-V]].

Pre-orders started on the 13th of April 2023, with pricing starting at USD 159 for the 4GB/64GB version and USD 209 for the 8GB/128GB version. The PineTab2 began shipping on June 2, 2023.

== Getting started ==

The PineTab2 box contains two smaller boxes.

The first box includes:

* The PineTab2
* Short user guide
* Power cable
* The UART adapter board

Note that the UART adapter is in the same package as the power cable, in a second compartment, and can be a bit hidden.

The second box has the keyboard in it.

=== First start ===

The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated.

{{Info|If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below.}}

The PineTab2 ships with ''DanctNix Arch Linux'' and comes with a pre-set user and the default password <code>123456</code>.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm / 123456</code>
|}

You can create a new user and set your own password after the initial boot. To do so, go to ''system settings'' -> ''users'' and create a new profile using your preferred name and password.

=== Keyboard cover ===

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.
The external keyboard has 5 connection pins (the golden pins). four are standard USB connectors and one is used to detect that the keyboard is connected.

The backlight can be changed with the key combination ''Pinekey + Ctrl (right)''.

== Software ==

All operating systems for the PineTab2 are delivered by community developers and partner projects. Aside from the operating system that comes pre-installed on your device, you can install and run any other operating system available for the PineTab2. Most, if not all operating systems for the PineTab2 are open and free, such as Linux and BSD.

Since most software issues will be release-specific, please see the [[PineTab2 Releases]] page for additional software related instructions, tips, and tricks.

=== Releases ===

The releases for the PineTab2 can be found under [[PineTab2 Releases]].

=== Installation instructions ===

The PineTab2 is capable of running different operating systems from the internal flash memory (eMMC) and from microSD card.

'''Preparing the microSD card'''

To write an operating system to the microSD card (typically called "flashing" in the community), you need to first download a compatible image from the [[#Releases|releases]] section.

Next you need to decompress the downloaded image. The images are typically compressed in an archive format such as ''xz'' to reduce the download size. If you are using a graphical tool such as ''balenaEtcher'' or ''Gnome Disks'' it will handle the decompression of the image in the flashing step automatically.

Further you need to flash the image to the microSD card. This can be done using various tools, for example ''balenaEtcher'' (recommended for new users), ''Gnome Disks'' or command-line tools such as ''cp'' and ''dd''. Insert the microSD card in a microSD card reader connected to your computer and then choose a tool of your liking.

Graphical applications:

* '''balenaEtcher''' (Microsoft Windows, macOS, Linux): Click on ''Flash from file'' and select the image. Then select the microSD card target device and click on ''Flash!''.

* '''Gnome Disks''' (Linux): Select the microSD card target device on the left side in the ''Disks'' list. Then select the three dot menu on the top right and click on ''Restore Disk Image...''. Select the image, verify the correct device is selected and then click on ''Start Restoring...''.

Command-line tools:

* '''cp''': <code>sudo cp '''IMAGE.img''' /dev/'''[DEVICE]'''</code>

* '''dd''': <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>

{{Info|Make sure to replace '''IMAGE.img''' and '''[DEVICE]''' with the filename of the image (double check if it is decompressed and has the file extension ''.img'') and the device name. You can use the command <code>lsblk</code> to find the device name. Make sure to flash to the whole device instead of partition 1 and that you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target. Be very careful to select the correct device, as the tools can overwrite your data when the wrong device is selected.}}

Then insert the microSD card into the PineTab2.

[[File:PineTab2 USB UARTv2.jpg|thumb|right|400px|Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image.]]

{{Hint|'''Note regarding the boot order:''' The SPI and the internal memory (eMMC) have a higher boot priority than the microSD card. The pre-installed bootloader on the internal memory (eMMC) tries to boot from the microSD card first. '''In some cases''' it can be required to bypass the bootloader, for example if the bootloader is corrupted or was overwritten by a bootloader with varying settings. 

To force the device to boot from the microSD card, the eMMC and the SPI can be disabled by using the debug UART adapter shipped with the device in the box also containing the charging cable. Set the ''SD BOOT MASKROM'' switch on the adapter to the position ''ON'' and plug it into the USB/PD charging port. Then power on the tablet and '''unplug the debug board or set the switch to the position ''OFF'' again''' when the factory image is started, otherwise the factory image won't find the eMMC.}}

Power on the device with the microSD card inserted (and optionally with the USB UART adapter inserted and the bypass switch set to ''ON'' depending on the software situation, see the info box above). It should now boot the new operating system from the microSD card.

'''Something is not working?''' Please join the [[Main_Page#Chat_Platforms|PineTab channel in the community chat]], the community is always happy to help. In the section [[#Connecting the UART adapter]] you can find information about how to connect the USB UART adapter and how to retrieve the boot logs if the device is not booting properly even after the above procudere.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|thumb|400px|right|Tablet's side ports: USB-C (with PD), MicroSD, USB-C 3.0, volume rocker, power button]]
* '''SoC:''' Rockchip RK3566
* '''CPU:''' 4x ARM Cortex-A55 @ 1.8 GHz
** 32KB L1 Instruction Cache and 32KB L1 Data Cache per core
** 512KB unified system L3 cache
** ARMv8 Cryptography Extensions
* '''GPU:''' Mali-G52 MP2 @ 800 MHz
** Supported by the open source 'Panfrost' driver in Linux and Mesa
** Supports OpenGL 3.1 and OpenGL ES 3.1 with many newer extensions
* '''NPU:''' 0.8 TOPS Neural Processing Unit
* '''RAM:''' 4GB or 8GB LPDDR4
* '''Storage:'''
** 64GB or 128GB internal eMMC ([https://www.szyuda88.com/product-77313-276594.html SiliconGo SGM8 100C-S36BCG]; eMMC 5.1, up o 400MB/s)
** 1x MicroSD slot
* '''Display:''' 10.1" IPS LCD Resolution 1280x800
* '''Cameras:'''
** Front: 2Mpx, chipset: Galaxycore GC02M2
** Rear: 5Mpx, chipset: Omnivision OV5648
* '''Battery:''' 6000 mAh (22.2Wh)
* '''Buttons:''' Power, volume up, volume down
* '''Network:'''
** Wi-Fi: BES2600
*** Driver under development, use a USB wifi dongle for now
** Bluetooth: BES2600
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 + PD (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 4 pole 3.5mm audio jack (microphone right) and headphone detection
** 2x speakers + microphone (microphone left)
** 1x 5 pin (USB 2.0; <=680mA) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''Sensors:'''
** Accelerometer: Silan SC7A20
** Ambient Light & Proximity Sensor
* '''Multimedia:'''
** rkdjpeg: 1080p120 JPEG decode
*** no driver in mainline yet
** hantro: JPEG/VP8/H.264 encode, 1080p MPEG-2/H.263/VP8/H.264 AVC decode
*** mainline driver does not yet support all codecs/functions
*** see [[Mainline Hardware Decoding]] and [[Mainline Hardware Encoding]]
** rkvdec2: 4K H.264 AVC Main10 L5.1/H.265 HEVC Main10 L5.1/VP9 Profile 0 and 2 L5.1 decode
*** no driver in mainline yet
** rkvenc2: 4K H.264 AVC/H.265 HEVC encode
*** no driver in mainline yet
* '''Build:''' Metal and Plastic
* '''Dimensions:''' 242x161x9mm
* '''Weight:''' 538g
* '''Misc:'''
** Protective cover with keyboard

== Development efforts ==

{{SeeMainArticle|Quartz64 Development}}

Linux mainline is already quite far along for the device, as the SoC is the same as is used in the Quartz64 line of devices. Some minor pinetab2-specific adjustments can be found [https://github.com/TuxThePenguin0/linux/tree/device/pine64-pinetab2_stable here] Check the main article for the big picture; PineTab2 specific issues are listed here.

=== Known Issues ===

* WiFi/Bluetooth chip BES2600:
** The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[PineTab2_FAQ#Performing_USB_Tethering_with_an_Android_Phone|USB tether a phone]] or [[PineTab2_FAQ#Selecting_a_USB_WIFI_Adapter|use a supported WI-FI dongle]]. There are at least two code releases available, with two respective/non-interchangeable firmware versions. The latest danctnix kernel has a pretty well working wifi driver.
** The BES2600 Bluetooth driver needs to be implemented.
** Hardware bugs - the power and reset circuitry is not properly implemented in the circuitry, so hard reset of the chip (in the theoretical case it freezes) is impossible without power cycling the whole board.
* The camera drivers needs to be ported ([https://github.com/rockchip-linux/kernel/blob/develop-4.19/drivers/media/i2c/gc02m2.c gc02m2], [https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c ov5648]), Rockchip CSI/ISP driver needs to be extended to handle 2 lanes.
* Suspend does not currently work reliably due to a driver issue. It is therefore disabled in the factory image. Caveat Emptor if you chose to unmask the feature prior to it being fixed.

=== Connecting the UART adapter ===

The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot:

* Plug the adapter face-up in the USB-C port furthest away from the power button. If all the lights are lit, you have the wrong port: only the green light should be lit when you first plug it in.
* Plug USB-C cable into the port on the adapter marked "DEBUG"
* Open a terminal window
* Install ''minicom'' or ''screen'' via your distribution's package manager, if you don't have it installed already
* Connect via minicom using <code>sudo minicom -D /dev/ttyUSB0 -b 1500000</code> or via screen using <code>sudo screen /dev/ttyUSB0 1500000</code>
** Ubuntu-based distro users may encounter the error, "cannot open /dev/ttyUSB0: No such file or directory". If this occurs, check the output of <code>sudo dmesg --follow</code> and unplug/replug the USB to look for any errors. If you see an error like, "usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1", then the brltty service is likely conflicting with this device. Brltty provides access to blind users who use a braille display: if you do not need this service, try disabling it using these commands:
*** <code> sudo systemctl stop brltty-udev.service</code>
*** <code> sudo systemctl mask brltty-udev.service</code>
*** <code> sudo systemctl stop brltty.service</code>
*** <code> sudo systemctl mask brltty.service</code>

== Board information, schematics and certifications ==

[[File:PPineTab2-pcb.jpg|thumb|right|PineTab2 Board]]

PineTab2 mainboard schematic:

* [https://files.pine64.org/doc/PineTab/PineTab2_V2_schematic-20230417.pdf PineTab2 mainboard Released Schematic-20230417 ver 2.0]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_top-20230417.pdf PineTab2 PCB Component Reference location v2.0 (top layer)]
* [https://files.pine64.org/doc/PineTab/PineTab2_V2_comp_ref_bottom-20230417.pdf PineTab2 PCB Component Reference location v2.0 (bottom layer)]
* [https://files.pine64.org/doc/PineTab/pinetab2-V_uart_console_schematic-20221107.pdf PineTab2/PineTab-V UART Dongle Schematic-20221107]

PineTab2 certifications:
* [https://files.pine64.org/doc/cert/Pinetab2%20FCC-SDOC%20Certificate-LCSA040323223E.pdf PineTab2 FCC Certificate]
* [https://files.pine64.org/doc/cert/Pinetab2%20CE%20RED%20Certificate-LCSA040323224E.pdf PineTab2 CE RED Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20CE%20EMC%20Certificate-LCSA040323225E.pdf PineTab2 CE EMC Certificate]
* [https://files.pine64.org/doc/cert/PineTab2%20ROHS%20Report-LCSA040323221R.pdf PineTab2 ROHS Test Report]
* [https://files.pine64.org/doc/cert/PineTab2%20Keyboard%20CE%20EMC%20Certificate-LCSA062623001E.pdf PineTab2/PineTab-V Detached Keyboard CE EMMC 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]
* [https://opensource.rock-chips.com/images/2/26/Rockchip_RK3568_TRM_Part1_V1.3-20220930P.PDF Rockchip RK3566 and RK3568 TRM (Technical Reference Manual)]

LCD panel:

* [[:File:Boe-technology-th101mb31ig002-28a-datasheet-v10.pdf|BOE TH101MB31IG002-28A datasheet v1.0]]

== Tutorials and Frequently Asked Questions ==

Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

There's also [[:File:PineTab2_display_panel_disassembly_guide.pdf|PineTab2 disassembly guide]]. The disassembly is a very delicate operation, especially around the corners of the screen. Several (even experienced) users ended up damaging the screen.

== External Links ==

* [https://www.pine64.org/2022/12/15/december-update-merry-christmas-and-happy-new-pinetab/ December 2022 Community Update]
* [https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ February 2023 Community Update]

[[Category:Rockchip RK3566]]