PINE64 - User contributions [en]

PineTab2

2023-10-23T11:16:04Z

Andree: /* Known Issues */ bes2600 bugs/info

[[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,
* a short user guide,
* a power cable and
* the UART adapter. 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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* wifi/bt 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 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]

PineTab2 disassembly guide:
* [[file:PineTab2_display_panel_disassembly_guide.pdf]]
* Note: this is a very delicate operation esp. around the corners of the screen. Several (even experienced) users ended up damaging the screen.

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

== Tutorials and Frequently Asked Questions ==
Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

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

User:Andree

2023-10-13T07:59:45Z

Andree:

* [https://wiki.t-firefly.com/en/ROC-RK3566-PC/driver_camera.html rk3566 camera DTS example, inspiration for pinetab2]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/tree/master/PKGBUILDS/pine64/uboot-pinetab2 uboot pkgbuild] | [https://github.com/Kwiboo/u-boot-rockchip/tree/2e0e11b8e65c48a43270f4ec4a88b74c8a83e269 uboot src]
* [https://gitlab.com/TuxThePenguin0/bes2600 bes2600 driver] , [https://gitlab.com/arjanvlek/bes2600/-/blob/test/README.md#14-compile-the-dtb-file howto]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/linux-pinetab2/PKGBUILD linux pkgbuild] | [https://github.com/dreemurrs-embedded/linux-pinetab2/tree/v6.4.3-danctnix1 linux src]
* [https://archmobile.mirror.danctnix.org/ packages]

PineTab2

2023-07-20T07:26:12Z

Andree: /* Board information, schematics and certifications */

[[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. Similarly packaged RISC-V tablet is [[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,
* a short user guide,
* a power cable and
* the UART adapter. 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 PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no stable releases. All releases for the PineTab2 will be listed under [[PineTab2 Releases]] as they're released. Your contributions are wanted!

=== 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|400px|right]]
* '''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
** Bluetooth
* '''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
** 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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* 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 [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* 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]

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

PineTab2 disassembly guide:
* [[file:PineTab2_display_panel_disassembly_guide.pdf]]
* Note: this is a very delicate operation esp. around the corners of the screen. Several (even experienced) users ended up damaging the screen.

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

== Tutorials and Frequently Asked Questions ==
Please see the [[PineTab2 FAQ]] page for tutorials and frequently asked questions.

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

File:PineTab2 display panel disassembly guide.pdf

2023-07-20T07:23:15Z

Andree: PineTab2 disassembly guide (published on telegram by tl_lim)

== Summary ==
PineTab2 disassembly guide (published on telegram by tl_lim)
== Licensing ==
{{subst:Unknown_copyright}}

User:Andree

2023-07-18T20:03:34Z

Andree:

* [https://wiki.t-firefly.com/en/ROC-RK3566-PC/driver_camera.html rk3566 camera DTS example, inspiration for pinetab2]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/tree/master/PKGBUILDS/pine64/uboot-pinetab2 uboot pkgbuild] | [https://github.com/Kwiboo/u-boot-rockchip/tree/2e0e11b8e65c48a43270f4ec4a88b74c8a83e269 uboot src]
* [https://gitlab.com/TuxThePenguin0/bes2600 bes2600 driver]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/linux-pinetab2/PKGBUILD linux pkgbuild] | [https://github.com/dreemurrs-embedded/linux-pinetab2/tree/v6.4.3-danctnix1 linux src]
* [https://archmobile.mirror.danctnix.org/ packages]

User:Andree

2023-07-18T19:48:13Z

Andree:

* [https://wiki.t-firefly.com/en/ROC-RK3566-PC/driver_camera.html rk3566 camera DTS example, inspiration for pinetab2]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/tree/master/PKGBUILDS/pine64/uboot-pinetab2 uboot pkgbuild] | [https://github.com/Kwiboo/u-boot-rockchip/tree/2e0e11b8e65c48a43270f4ec4a88b74c8a83e269 uboot src]
* [https://gitlab.com/TuxThePenguin0/bes2600 bes2600 driver]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/linux-pinetab2/PKGBUILD linux pkgbuild] | [https://github.com/dreemurrs-embedded/linux-pinetab2/tree/v6.4.3-danctnix1 linux src]

Quartz64 Development

2023-07-14T20:37:58Z

Andree: /* Upstreaming Status */ +rknpu link

This page documents the current status of software support for the [[Quartz64]] single-board computer, and provides links to resources to help prospective contributors get started. Information is kept current on a best-effort basis as various patches get accepted into the kernel.

== Overview ==

=== Upstreaming Status ===

{| class="wikitable plainrowheaders" border="1"
! scope="col" | Function
! scope="col" colspan="2" | Status
! scope="col" | Component
! scope="col" | Notes
! scope="col" | Applies To
|-
! scope="row" rowspan="3" | Video Output
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchipdrm/VOP2</code>
|
As of 5.19-rc1[https://git.kernel.org/linus/604be85547ce4d61b89292d2f9a78c721b778c16], Also featured in Phoronix Article[https://www.phoronix.com/scan.php?page=news_item&px=Rockchip-VOP2-Linux-5.19]
|-
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rockchip-edpphy-naneng</code>
| Downstream: [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/blob/quartz64/drivers/phy/rockchip/phy-rockchip-naneng-edp.c] and [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/commit/d7ad116fb30d11d110aeb880754cf27f34c45c40#7e8e2ef87e479c54539dc519c0b92d6b31727f8d_671_681] Coordinate any porting with Rockchip first
|
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>dw-mipi-dsi-rockchip</code>
| As of 6.1[https://git.kernel.org/linus/e18d9b093006d8abd53e1ce13c0d5a8d0fcd5f64]
|
|-
! scope="row" | 3D Acceleration
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
| <code>panfrost</code>
| As of 5.18[https://git.kernel.org/linus/810028668c6d9da25664195d6b906c98a8169f72]
|-
! scope="row" rowspan="3" | Video Decode
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="background:LightYellow; text-align:center;" rowspan="3"|GStreamer only, no ffmpeg[https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=2898]
| <code>hantro</code> using <code>v4l2-requests</code>
| VDPU121 handling 1080p MPEG-2, VP8 and H.264. Mainline as of 5.19[https://git.kernel.org/linus/5f6bfab6da6531238e899fdf29efd6d0185adc3e]
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| <code>rkvdec2</code> using <code>v4l2-requests</code>
| VDPU346 handling 4K H.265, H.264 and VP9
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| <code>rkdjpeg</code> using <code>v4l2-requests</code>
| VDPU720 handling JPEG, [[User:CounterPillow]] is working on this
|-
! scope="row" rowspan="5" | [[Mainline Hardware Encoding|Video Encode]]
| style="background:PaleGreen; text-align:center;"|Linux Mainline
| style="text-align:center; background:LightYellow;"|GStreamer only
| JPEG on VEPU121
| Hantro-based. Mainline as of 6.1[https://git.kernel.org/linus/6f1ae821a6c4aa9d5b8f437b27ec86fb569219fd]
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.264 on VEPU121
| Hantro-based
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| VP8 on VEPU121
| Hantro-based
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.264 on VEPU540
| rkvenc-based
|
|-
| style="background:#F99; text-align:center;"|Needs writing
| style="text-align:center;"|?
| H.265 on VEPU540
| rkvenc-based
|
|-
! scope="row" rowspan="3" | Audio
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-i2s-tdm</code>
| As of 5.16[https://git.kernel.org/linus/43b058698f723e3c2087af7069c0da082a3ecbe1]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-spdif</code>
| As of 5.15[https://git.kernel.org/linus/dac825b6a6bdca41347e25f07354ad94fdc97445]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk817-codec</code>
| As of 5.14[https://git.kernel.org/linus/0d6a04da9b25b9a7cf2cac5f5079e3296d3bee0f].
| Quartz64 Model A/B
|-
! scope="row" rowspan="3" | Bootloader
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/16952]
| <code>TF-A</code>
|
|-
| colspan="2" style="background:LightYellow; text-align:center;"|In progress
| <code>U-Boot</code>
| [[Quartz64_Development#Mainline_U-Boot_Work|See below]]
|
|-
| colspan="2" style="background:LightYellow; text-align:center;"|In progress[https://github.com/jaredmcneill/quartz64_uefi]
| <code>Tianocore EDK II</code>
|
|-
! scope="row" rowspan="4" | Device Tree
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| Quartz64 Model A
| As of 5.16[https://git.kernel.org/linus/b33a22a1e7c4248608e533fc4fa524258b3fae84]
| Quartz64 Model A
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| Quartz64 Model B
| As of 5.19[https://git.kernel.org/linus/c37415f55bdadffe5b4c0e7981e9fc7e8b96beea]
| Quartz64 Model B
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| SOQuartz
| As of 5.19[https://git.kernel.org/linus/c466828fb3ba8cb7f5c3bf28766da9b70bf9745e]
| SOQuartz
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| PineNote
| As of 5.18[https://git.kernel.org/linus/d449121e5e8addcee654250cec298c887ecafb32]
| PineNote
|-
! scope="row" rowspan="2"| Gigabit Ethernet
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk3566-gmac</code>
| As of 5.14[https://git.kernel.org/linus/3bb3d6b1c1957e88bfc5e77a4557f7e6ba761fe3]
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>yt8511-phy</code>
| As of 5.14[https://git.kernel.org/linus/48e8c6f1612b3d2dccaea2285231def830cc5b8e]
|-
! scope="row" | IOMMU
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-iommu</code>
| As of 5.14[https://git.kernel.org/linus/c55356c534aa651ccc3053ef2d5d8d810adacf5f]
|-
! scope="row" | GPIO
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>gpio-rockchip</code>
| As of 5.15[https://git.kernel.org/linus/936ee2675eee1faca0dcdfa79165c7990422e0fc]
|-
! scope="row" | pinctrl
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
|
|
|-
! scope="row" | Thermal Regulation
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-thermal</code>
| As of 5.14[https://git.kernel.org/linus/4b14c055a6f644cbeb1156ba24647e92fe51ec69]
|-
! scope="row" | PCIe
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>pcie-dw-rockchip</code>
| As of 5.15[https://git.kernel.org/linus/0e898eb8df4e34c7b129452444eb7cef68a11f43]
|-
! scope="row" | Power Management
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-pm-domains</code>
| As of 5.14[https://git.kernel.org/linus/1782c87b44a0b1a527f01a6a184677c58ccbf9c7]
|-
! scope="row" | Voltage Control
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk3568-pmu-io-voltage-domain</code>
| As of 5.15[https://git.kernel.org/linus/28b05a64e47cbceebb8a5f3f643033148d5c06c3]
|-
! scope="row" | SPI
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>spi-rockchip</code>
| As of 5.14[https://git.kernel.org/linus/d74d99229f4d48f42d674f7a8a1137179efd67ac]. Necessary device tree changes [https://patchwork.kernel.org/project/linux-rockchip/list/?series=586691 in review].
|-
! scope="row" | Battery
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rk817-charger</code>
| As of 6.1[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/power/supply/rk817_charger.c?id=11cb8da0189b417392e2334ae967b0ba1f0d1be8]
| Quartz64 Model A, Pinenote
|-
! scope="row" | Microphone
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-saradc</code>
| As of 5.15[https://git.kernel.org/linus/7786da3b5ae167c17f35e22ba35e06006338c2f6]. Headphone jack mic seems to connect to <code>SARADC_VIN2_HP_HOOK</code>, so I'm pretty sure that the dtsi and driver changes are needed for that mic to work
|-
! scope="row" | USB 2.0
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-usb2phy</code>
| As of 5.17[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/phy/rockchip?h=v5.17-rc1&id=42b559727a45d79c811f493515eb9b7e56016421]
|-
! scope="row" | e-Ink
| colspan="2" style="background:LightYellow; text-align:center;"|In review (RFC)[https://lore.kernel.org/linux-rockchip/20220413221916.50995-1-samuel@sholland.org/T/]
| <code>rockchip-ebc</code>
| A DRM driver is available [https://github.com/smaeul/linux/commits/rk35/ebc-drm-v5 here]; also see [[RK3566 EBC Reverse-Engineering]]
|-
! scope="row" | Combo PHY
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>naneng-combphy</code>
| As of 5.18[https://git.kernel.org/linus/7160820d742a16313f7802e33c2956c19548e488]. Still requires DTS changes
|-
! scope="row" | RGA
| colspan="2" style="background:#F99; text-align:center;"|Needs fixing
| <code>rockchip-rga</code>
| [[User:CounterPillow]] experimentally enabled it[https://gist.github.com/CounterPillow/6bea809f15ada7ddd3a3d7a4994fdc4e] in the device tree and ran gstreamer's v4l2convert through it to test, resulting in a completely garbled output.
|-
! scope="row" | Fan Controller
| colspan="2" style="background:#F99; text-align:center;"|Needs writing
| <code>gp7101</code>
| Someone should write a pwm driver for it so we can then use pwm-fan
| SOQuartz Blade
|-
! scope="row" rowspan="2" | CSI Camera
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rkisp</code>
| Downstream: [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/tree/quartz64/drivers/media/platform/rockchip/isp]
|
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>rockchip-inno-csidphy</code>
| As of 6.1[https://git.kernel.org/linus/29c99fb085ad53e6d5504d1f8d32e6673b9b3a2c]
|
|-
! scope="row" | NPU
| colspan="2" style="background:#F99; text-align:center;"|Needs writing
|
| Downstream version is a closed source SDK and [https://github.com/dieselnutjob/kernel-rk3566/tree/linux-4.19.210/drivers/rknpu open source kernel module rknpu]. Major undertaking to reimplement this as Linux does not (yet) appear to have a generic architecture for neural accelerators.
|
|-
! scope="row" | Crypto
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>rk-crypto</code> v2
| Downstream driver [https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux/-/tree/quartz64/drivers/crypto/rockchip] doesn't include a rk3568 compatible either, but the TRM shows that it seemingly matches.
|
|-
! scope="row" | TRNG
| colspan="2" style="background:LightYellow; text-align:center;"|In review[https://patchwork.kernel.org/project/linux-rockchip/list/?series=699813]
| <code>rockchip-rng</code>
|
|
|-
! scope="row" rowspan="2" | Wi-Fi
| colspan="2" style="background:#F99; text-align:center;"|Needs porting
| <code>bes2600</code>
| A downstream driver is available but it makes use of some custom Rockchip interfaces and is designed for older kernels, plans are being made to port it to DKMS.
| PineTab 2
|-
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
| <code>brcmfmac</code>
|
| Quartz64 Model B
|}

== Current Status ==

The following sections give an overview over the current status of different parts of the board. Some parts are waiting on a driver to be written or ported, others only need various adjustments.

According to pgwipeout, I/O device performance is within expected ranges now.

=== Working ===

* eMMC
* SDMMC0 (SD cards)
* GMAC (Gigabit Ethernet)
* USB 2.0
* SATA 2
* SATA 3
* UART
** UART 0 (Pi-bus)
** UART 1 (Bluetooth)
** UART 2 (Pi-bus, debug)
* Video Decode
** VP8
** H.264
* Video Encode
** JPEG (it's pretty bad)
* Battery
* GPU
* Audio
** Analog audio works
** SPDIF works
** HDMI works
* SPI — works, user needs to modify device tree to add devices
* I2C — works, user needs to modify device tree to add devices

=== Partially Working ===

* PCI-Express Controller — everything but devices that need cache coherency (e.g. dGPUs) should work
** [[User:CounterPillow]] noticed some weirdness with NVMe devices disconnecting during heavy write operations, likely down due to power draw on one of the rails as the same sustained bandwidth could be achieved with a different PCIe device with no issue.
* SDMMC1 (Wi-Fi) — AP6256 working, BL602 needs some work to make it flash firmware
* [https://developer.arm.com/architectures/system-architectures/system-components/arm-generic-interrupt-controller GIC] — needs errata published by Rockchip to get upstream to add device-specific workarounds[https://lore.kernel.org/linux-rockchip/CAMdYzYrQ5f-mv_VmTq_CRf9tR=j3mwRpKHNLmPFgCF9whsGFRw@mail.gmail.com/]
* Video Output — only at 1920x1080p60 and nothing else, very buggy and rough around more than just the edges

=== Confirmed Broken ===

* USB 3.0 (applies to Model A only) — only works with very short cables and depends on the device. This is due to a hardware design issue relating to the coupling capacitors needed for SATA, which shares the same lines as USB 3.0.
** Hardware design changes have been suggested to engineers, it's in their hands now.
* RGA — only works with memory ≤ 4 GiB, because Rockchip didn't make the address registers larger. Oopsie.

=== Needs Testing ===

* E-Paper
* Microphone Input
* CSI — needs CIF driver
* eDP — needs PHY driver and controller driver
* DSI

== TODO ==

=== ebc-dev Reverse Engineering and Development ===

The [https://gitlab.com/pine64-org/quartz-bsp/linux-next/-/tree/rk356x-ebc-dev driver for the eInk panel] needs to both be reverse engineered and then rewritten as C. In its current form, it is mostly an assembly dump produced by gcc with debug symbols. See [[RK3566 EBC Reverse-Engineering]] for details.

=== Investigate MCU ===

The RK3566 comes with an integrated RISC-V microcontroller (MCU). It communicates with the A55 host through the Mailbox system driven by the rockchip-mailbox driver. Since this MCU would be quite useful for things such as low power standby mode, investigating how it can be turned on and have firmware flashed to it should greatly enhance the power saving features of the PineNote.

=== Mainline U-Boot Work ===

We currently use the "downstream" Rockchip U-Boot, which is based on an old version of U-Boot and contains vendor specific patches that have not undergone the same level of code review as they'd have done had they been submitted upstream.

While the lack of ATF sources means that using mainline U-Boot would still require the use of Rockchip provided binaries for the firmware, even with Rockchip blobs, a more modern version of U-Boot will be much nicer to use.

Mainline U-Boot contains good enough support for the RK3566 SoC used on the Quartz64 as of v2023.07, patches are still in review for e.g. PCIe/NVMe/AHCI support.

==== Things that need to be done ====

This list is non-exhaustive as we don't exactly know how much is missing

* Bring the kernel's Quartz64 DTSes into the tree (CounterPillow did this [https://github.com/CounterPillow/u-boot-quartz64/commits/mainline-ish-2 in his tree], Kwiboo refined this [https://github.com/Kwiboo/u-boot-rockchip/commits/rk3568-2023.07 in his tree])
* Write <code>defconfig</code>s based on <code>evb-rk3568_defconfig</code> (CounterPillow did this [https://github.com/CounterPillow/u-boot-quartz64/commits/mainline-ish-2 in his tree], Kwiboo refined this [https://github.com/Kwiboo/u-boot-rockchip/commits/rk3568-2023.07 in his tree])

Stretch Goals:

* Port the Motorcomm PHY driver to u-boot for networking
** Only needed for Model A, RTL8211 on Model B is already supported in mainline u-boot
* Port a basic VOP2 driver to get a framebuffer from u-boot

==== List of Useful Resources for this Task ====
* Downstream Rockchip U-Boot repository with Quartz64 specific patches: https://gitlab.com/pgwipeout/u-boot-rockchip/-/tree/quartz64
* Mainline Rockchip custodian U-Boot repository: https://source.denx.de/u-boot/custodians/u-boot-rockchip
* U-Boot Mailing List: https://lists.denx.de/listinfo/u-boot

=== eDP Driver Porting ===

The eDP PHY driver and controller driver needs to be ported, brought into shape and submitted with proper commit attribution to the Rockchip authors.

[[User:CounterPillow]] has experimentally ported stuff, but it's currently not working.

== Linux Kernel Config Options ==

* <code>CONFIG_SND_SOC_ROCKCHIP_I2S_TDM</code>
** for Analog and HDMI audio
* <code>CONFIG_SND_SOC_RK817</code>
** for Analog audio on the Model A
* <code>CONFIG_STMMAC_ETH</code>
** Ethernet
* <code>CONFIG_DWMAC_ROCKCHIP</code>
** Ethernet
* <code>CONFIG_MOTORCOMM_PHY</code>
** Ethernet PHY for Model A, set this one to Y, m won't work out of the box if the generic PHY driver is y and binds first. Alternatively tell users in board-specific setup instructions to force including the <code>motorcomm</code> module in initramfs if you set it to m.
* <code>CONFIG_REALTEK_PHY</code>
** Ethernet PHY for Model B
* <code>CONFIG_MMC_DW</code>
** MMC/SD
* <code>CONFIG_MMC_DW_ROCKCHIP</code>
** MMC/SD
* <code>CONFIG_MMC_SDHCI_OF_DWCMSHC</code>
** MMC/SD
* <code>CONFIG_PCIE_ROCKCHIP_DW_HOST</code>
** PCIe
* <code>CONFIG_PHY_ROCKCHIP_NANENG_COMBO_PHY</code>
** PHY for PCIe/SATA/USB3
* <code>CONFIG_DRM_PANFROST</code>
** GPU
* <code>CONFIG_SND_SOC_ROCKCHIP_SPDIF</code>
** SPDIF audio
* <code>CONFIG_ROCKCHIP_DW_HDMI</code>
** HDMI PHY
* <code>CONFIG_PHY_ROCKCHIP_INNO_DSIDPHY</code>
** MIPI DSI DPHY
* <code>CONFIG_ROCKCHIP_VOP2</code>
** Video output
* <code>CONFIG_ARCH_ROCKCHIP</code>
** General SoC support
* <code>CONFIG_ROCKCHIP_PHY</code>
** General SoC support
* <code>CONFIG_PHY_ROCKCHIP_INNO_USB2</code>
** USB 2
* <code>CONFIG_RTC_DRV_RK808</code>
** Real-time Clock
* <code>CONFIG_COMMON_CLK_RK808</code>
** Real-time Clock
* <code>CONFIG_MFD_RK808</code>
** Various things relating to the RK817 chip
* <code>CONFIG_CHARGER_RK817</code>
** RK817 charger
* <code>CONFIG_REGULATOR_RK808</code>
** Voltage regulators
* <code>CONFIG_ROCKCHIP_PM_DOMAINS</code>
** Power management domains
* <code>CONFIG_GPIO_ROCKCHIP</code>
** GPIO support
* <code>CONFIG_PINCTRL_ROCKCHIP</code>
** GPIO and general SoC support
* <code>CONFIG_PWM_ROCKCHIP</code>
** PWM support
* <code>CONFIG_ROCKCHIP_IOMMU</code>
** IOMMU support
* <code>CONFIG_ROCKCHIP_MBOX</code>
** Mailbox support (for communication with MCU)
* <code>CONFIG_ROCKCHIP_SARADC</code>
** Analog-to-digital conversion support, for e.g. microphones
* <code>CONFIG_ROCKCHIP_THERMAL</code>
** Temperature sensor and thermal throttling support
* <code>CONFIG_SPI_ROCKCHIP</code>
** SPI support
* <code>CONFIG_VIDEO_HANTRO_ROCKCHIP</code>
** Hardware video decoder support
* <code>CONFIG_ROCKCHIP_IODOMAIN</code>
** General SoC support so your I/O pins have the right voltage
* <code>CONFIG_COMMON_CLK_ROCKCHIP</code>
** Common clock support
* <code>CONFIG_PHY_ROCKCHIP_INNO_CSIDPHY</code>
** MIPI CSI DPHY
* <code>CONFIG_I2C_RK3X</code>
** I2C support

== Resources ==
=== Repositories ===

* pgwipeout's kernel tree
** https://gitlab.com/pgwipeout/linux-next/-/tree/quartz64-v5.15-rc1
* BSP based development effort for SPL/U-Boot and Linux
** https://gitlab.com/pine64-org/quartz-bsp
* Image CI pipeline aimed at developers
** https://gitlab.com/pgwipeout/quartz64_ci/
* Rockchip U-Boot
** https://github.com/rockchip-linux/u-boot
* Downstream rockchip-linux kernel tree
** https://gitlab.com/pine64-org/quartz-bsp/rockchip-linux
* Tianocore EDK II port for UEFI on Quartz64
** https://github.com/jaredmcneill/quartz64_uefi
* Mainline U-Boot Port by pgwipeout
** https://gitlab.com/pgwipeout/u-boot-quartz64

=== Other ===

* Rockchip-SoC Patchwork Page
** https://patchwork.kernel.org/project/linux-rockchip/list/
* Rockchip Kernel Mailing List Archive
** https://lore.kernel.org/linux-rockchip/

== Board/SoC Documentation ==
=== Booting ===
==== Boot Order ====
The RK3566 boot ROM will search for a valid ID BLOCK in the following order on the support boot media:

* SPI NOR flash
* SPI NAND flash
* eMMC
* SD-Card

... if this fails, the boot ROM will initialize the USB0 port and wait for a connection from the Rockchip
flash/boot tools.

==== Bootloader Flashing ====

As per pgwipeout's [https://gitlab.com/pine64-org/quartz-bsp/u-boot/-/commit/12d102b86813378af08b086f3b9c13ed8010754c commit message]:
* Make a partition named <code>uboot</code> as partition number 1 at 8 MiB to 16 MiB
* <code>dd if=idblock.bin of=/dev/''<mmc/sd>'' seek=64</code>
* <code>dd if=uboot.img of=/dev/''<mmc/sd>''1</code>

==== BSP Image Layout ====

[[Category:Quartz64]][[Category:Rockchip RK3566]]

PineTab2 Releases

2023-06-26T05:51:41Z

Andree: alsa-ucm-pinetab2

This page contains a list of all available releases and tools for the [[PineTab2]] in alphabetical order.

The installation instructions can be found under [[PineTab2#Installation instructions]].

__TOC__

== Linux ==

=== Arch Linux ARM ===

(Unofficial) Arch Linux ARM maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

Download:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz

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

Notes:

* Currently ships without a Wi-Fi and Bluetooth driver
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)
* [https://forum.pine64.org/showthread.php?tid=18313 screen rotated 90°, workaround possible]
* [https://github.com/ScottFreeCode/Pine64-Arch/tree/master/PKGBUILDS/pine64/alsa-ucm-pinetab2 HP/Speaker switching via Alsa UCM]

=== Mobian ===
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh. The current version of the base Debian system is Debian Bookworm. See the installation instructions [https://wiki.debian.org/InstallingDebianOn/PINE64/PineTab2 here]. If you have questions about Mobian, please ask them in the [https://matrix.to/#/#mobian:matrix.org Mobian Matrix room].

Download:

* [https://images.mobian.org/pinetab2/ Images] (until the weekly images are built, you can download the PineTab2 image from [https://ci-images.mobian.org/20230619.0942/ here])

{{Info|U-Boot is required to be able to boot the images, see [https://github.com/Kwiboo/u-boot-build/suites/13552260933/artifacts/745702098 here] (you need a GitHub account to download it). Unless you are an experienced developer, it is recommended you instead put [https://ci-images.mobian.org/20230619.0715/mobian-pinetab2-phosh-20230619.img.gz this image] on an SD card and then [https://github.com/Kwiboo/u-boot-build#sd-card-or-emmc-module flash U-Boot to the SD card], as it's much safer. If you are an experienced developer and have read the warning below, follow the [https://github.com/Kwiboo/u-boot-build#spi-flash instructions] to flash U-Boot to the SPI of your PineTab2.}}

{{Warning|Flashing the SPI flash memory is a '''dangerous procedure''' because the SPI has the highest boot priority. Any bug or faulty installation in the SPI can prevent the device from booting, which means that there is a '''high risk of getting locked out of the device'''. The only way of restoring from that state is using a specialized UART adapter, which can disable the SPI flash memory at boot, as explained in the [[PineTab2#Installation instructions|''installation instructions'' section of the PineTab2 article]]. '''DO NOT FLASH THE SPI''' unless you are an experienced developer with access to the UART adapter and you have confirmed that the adapter is functional.}}

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

Notes:
* The development is work in progress. Mobian's support for the PineTab2 is maintained by [https://salsa.debian.org/julianfairfax Julian]. The Mobian wiki can be found [https://wiki.mobian-project.org/ here].
* In order to connect to the device using SSH/SCP, you need to install SSH on the device. You can do this by executing the following in a shell: "sudo apt-get install ssh", afterwards you can connect via SSH/SCP using the PineTab2's IP address on port 22.
* When installing Mobian with full disk encryption and booting with the keyboard case connected, you will have to touch the screen or press a key to show the decryption screen. This is an [https://gitlab.com/postmarketOS/osk-sdl/-/issues/148 upstream issue].



[[Category:Rockchip RK3566]]

PineTab2

2023-06-26T05:49:28Z

Andree: /* Development efforts */

[[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. Similarly packaged RISC-V tablet is [[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 package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. 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.

== 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 PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no stable releases. All releases for the PineTab2 will be listed under [[PineTab2 Releases]] as they're released. Your contributions are wanted!

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

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|400px|right]]
* '''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
** Bluetooth
* '''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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* 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 [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

No, adding a digitiser for pen inputs would make the price too high.

'''Can I run Android on it?'''

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

'''Is there SPI Flash?'''

Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

'''My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this?'''

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

'''How does the Tablet compare to a Pinebook Pro?'''

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

'''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.

'''Does PineTab2 play back DRM'd Content such as Netflix?'''

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

'''I only know Python, can I help with drivers?'''

Yes, if you learn C first. If that's too big of a hurdle, then no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, plug the included debug adapter into the charging USB-C port and switch the white switch to its "ON" position to bypass eMMC/SPI boot. This tries to boot from SD, and if no SD is inserted, enters Maskrom mode.

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

Make sure to open the iPhone once you reconnect.

==== Performing USB Tethering with a KaiOS phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use a KaiOS phone for mobile Internet use with your PineTab2.

You'll need:

* A KaiOS phone
* A USB OTG adapter (hama #00200311 tested)
* Your device’s charging cable
* Some knowledge of your KaiOS phone

Do the following in order:

* Plug the device into the PineTab2 using the USB cable and a USB OTG adapter
* On your KaiOS phone, open settings (specifics from here may vary on version)
* Navigate to "Network & Connectivity"
* Navigate to "Internet Sharing"
* Select "USB" and select On under USB tethering (Note: This option will be greyed out unless connected to the PineTab2)

You should now see a new network interface on the PineTab2 and it should show a wired connection icon.

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

2023-06-24T14:43:42Z

Andree: /* Known Issues */

[[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. Similarly packaged RISC-V tablet is [[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 package includes the PineTab2, a short user guide, a power cable and the UART adapter Note that the UART adapter is in the same package as the power cable in a second compartment and can be a bit hidden, search for it. 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.

== 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 PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no stable releases. All releases for the PineTab2 will be listed under [[PineTab2 Releases]] as they're released. Your contributions are wanted!

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

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|400px|right]]
* '''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
** Bluetooth
* '''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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] is basically operational, but needs major cleanup and bugfixing (at the moment it often causes system crashes). This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

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

== Frequently Asked Questions ==

'''Does the Tablet support a Pen?'''

No, adding a digitiser for pen inputs would make the price too high.

'''Can I run Android on it?'''

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

'''Is there SPI Flash?'''

Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

'''My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this?'''

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

'''How does the Tablet compare to a Pinebook Pro?'''

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

'''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.

'''Does PineTab2 play back DRM'd Content such as Netflix?'''

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

'''I only know Python, can I help with drivers?'''

Yes, if you learn C first. If that's too big of a hurdle, then no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, plug the included debug adapter into the charging USB-C port and switch the white switch to its "ON" position to bypass eMMC/SPI boot. This tries to boot from SD, and if no SD is inserted, enters Maskrom mode.

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

Make sure to open the iPhone once you reconnect.

==== Performing USB Tethering with a KaiOS phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use a KaiOS phone for mobile Internet use with your PineTab2.

You'll need:

* A KaiOS phone
* A USB OTG adapter (hama #00200311 tested)
* Your device’s charging cable
* Some knowledge of your KaiOS phone

Do the following in order:

* Plug the device into the PineTab2 using the USB cable and a USB OTG adapter
* On your KaiOS phone, open settings (specifics from here may vary on version)
* Navigate to "Network & Connectivity"
* Navigate to "Internet Sharing"
* Select "USB" and select On under USB tethering (Note: This option will be greyed out unless connected to the PineTab2)

You should now see a new network interface on the PineTab2 and it should show a wired connection icon.

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

2023-06-24T07:45:53Z

Andree: /* Arch Linux ARM */

This page contains a list of all available releases and tools for the [[PineTab2]] in alphabetical order.

The installation instructions can be found under [[PineTab2#Installation instructions]].

__TOC__

== Linux ==

=== Arch Linux ARM ===

(Unofficial) Arch Linux ARM maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).
This includes
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/uboot-pinetab2/PKGBUILD uboot]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/linux-pinetab2/PKGBUILD linux kernel]
* [https://github.com/TuxThePenguin0/linux/blob/872b829a3511cfa853bd3af3bd4f30be1cb3d1ab/arch/arm64/boot/dts/rockchip/rk3566-pinetab2-v2.0.dts device tree]
* package repository: [https://archmobile.mirror.danctnix.org/ here]...

Download:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz

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

Notes:

* Currently ships without a Wi-Fi and Bluetooth driver
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)
* [https://forum.pine64.org/showthread.php?tid=18313 screen rotated 90°, workaround possible]

=== Mobian ===
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh. The current version of the base Debian system is Debian Bookworm. See the installation instructions [https://wiki.debian.org/InstallingDebianOn/PINE64/PineTab2 here]. If you have questions about Mobian, please ask them in the [https://matrix.to/#/#mobian:matrix.org Mobian Matrix room].

Download:

* [https://images.mobian.org/pinetab2/ Images] (until the weekly images are built, you can download the PineTab2 image from [https://ci-images.mobian.org/20230619.0942/ here])

{{Info|U-Boot is required to be able to boot the images, see [https://github.com/Kwiboo/u-boot-build/suites/13552260933/artifacts/745702098 here] (you need a GitHub account to download it). Unless you are an experienced developer, it is recommended you instead put [https://ci-images.mobian.org/20230619.0715/mobian-pinetab2-phosh-20230619.img.gz this image] on an SD card and then [https://github.com/Kwiboo/u-boot-build#sd-card-or-emmc-module flash U-Boot to the SD card], as it's much safer. If you are an experienced developer and have read the warning below, follow the [https://github.com/Kwiboo/u-boot-build#spi-flash instructions] to flash U-Boot to the SPI of your PineTab2.}}

{{Warning|Flashing the SPI flash memory is a '''dangerous procedure''' because the SPI has the highest boot priority. Any bug or faulty installation in the SPI can prevent the device from booting, which means that there is a '''high risk of getting locked out of the device'''. The only way of restoring from that state is using a specialized UART adapter, which can disable the SPI flash memory at boot, as explained in the [[PineTab2#Installation instructions|''installation instructions'' section of the PineTab2 article]]. '''DO NOT FLASH THE SPI''' unless you are an experienced developer with access to the UART adapter and you have confirmed that the adapter is functional.}}

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

Notes:
* The development is work in progress. Mobian's support for the PineTab2 is maintained by [https://salsa.debian.org/julianfairfax Julian]. The Mobian wiki can be found [https://wiki.mobian-project.org/ here].
* In order to connect to the device using SSH/SCP, you need to install SSH on the device. You can do this by executing the following in a shell: "sudo apt-get install ssh", afterwards you can connect via SSH/SCP using the PineTab2's IP address on port 22.
* When installing Mobian with full disk encryption and booting with the keyboard case connected, you will have to touch the screen or press a key to show the decryption screen. This is an [https://gitlab.com/postmarketOS/osk-sdl/-/issues/148 upstream issue].



[[Category:Rockchip RK3566]]

PineTab2 Releases

2023-06-24T07:40:29Z

Andree: /* Arch Linux ARM */ add links to kernel/dts

This page contains a list of all available releases and tools for the [[PineTab2]] in alphabetical order.

The installation instructions can be found under [[PineTab2#Installation instructions]].

__TOC__

== Linux ==

=== Arch Linux ARM ===

(Unofficial) Arch Linux ARM maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).
This includes
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/uboot-pinetab2/PKGBUILD uboot]
* [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/linux-pinetab2/PKGBUILD linux kernel]
* [https://github.com/TuxThePenguin0/linux/blob/872b829a3511cfa853bd3af3bd4f30be1cb3d1ab/arch/arm64/boot/dts/rockchip/rk3566-pinetab2-v2.0.dts device tree]
* userspace packages...

Download:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz

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

Notes:

* Currently ships without a Wi-Fi and Bluetooth driver
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)
* [https://forum.pine64.org/showthread.php?tid=18313 screen rotated 90°, workaround possible]

=== Mobian ===
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh. The current version of the base Debian system is Debian Bookworm. See the installation instructions [https://wiki.debian.org/InstallingDebianOn/PINE64/PineTab2 here]. If you have questions about Mobian, please ask them in the [https://matrix.to/#/#mobian:matrix.org Mobian Matrix room].

Download:

* [https://images.mobian.org/pinetab2/ Images] (until the weekly images are built, you can download the PineTab2 image from [https://ci-images.mobian.org/20230619.0942/ here])

{{Info|U-Boot is required to be able to boot the images, see [https://github.com/Kwiboo/u-boot-build/suites/13552260933/artifacts/745702098 here] (you need a GitHub account to download it). Unless you are an experienced developer, it is recommended you instead put [https://ci-images.mobian.org/20230619.0715/mobian-pinetab2-phosh-20230619.img.gz this image] on an SD card and then [https://github.com/Kwiboo/u-boot-build#sd-card-or-emmc-module flash U-Boot to the SD card], as it's much safer. If you are an experienced developer and have read the warning below, follow the [https://github.com/Kwiboo/u-boot-build#spi-flash instructions] to flash U-Boot to the SPI of your PineTab2.}}

{{Warning|Flashing the SPI flash memory is a '''dangerous procedure''' because the SPI has the highest boot priority. Any bug or faulty installation in the SPI can prevent the device from booting, which means that there is a '''high risk of getting locked out of the device'''. The only way of restoring from that state is using a specialized UART adapter, which can disable the SPI flash memory at boot, as explained in the [[PineTab2#Installation instructions|''installation instructions'' section of the PineTab2 article]]. '''DO NOT FLASH THE SPI''' unless you are an experienced developer with access to the UART adapter and you have confirmed that the adapter is functional.}}

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

Notes:
* The development is work in progress. Mobian's support for the PineTab2 is maintained by [https://salsa.debian.org/julianfairfax Julian]. The Mobian wiki can be found [https://wiki.mobian-project.org/ here].
* In order to connect to the device using SSH/SCP, you need to install SSH on the device. You can do this by executing the following in a shell: "sudo apt-get install ssh", afterwards you can connect via SSH/SCP using the PineTab2's IP address on port 22.
* When installing Mobian with full disk encryption and booting with the keyboard case connected, you will have to touch the screen or press a key to show the decryption screen. This is an [https://gitlab.com/postmarketOS/osk-sdl/-/issues/148 upstream issue].



[[Category:Rockchip RK3566]]

PineTab2

2023-06-13T06:38:58Z

Andree: /* Specifications */ +side ports photo

[[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. Similarly packaged RISC-V tablet is [[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 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.

== 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 PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no stable releases. All releases for the PineTab2 will be listed under [[PineTab2 Releases]] as they're released. Your contributions are wanted!

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

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

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
[[File:Pinetab2-side.jpeg|400px|right]]
* '''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
** Bluetooth
* '''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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Yes! A 128 Mbit flash chip (sk25lp128) is reportedly present on production devices.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

=== I only know Python, can I help with drivers? ===

Yes, if you learn C first. If that's too big of a hurdle, then no. (This response isn't trying to be snarky, this question was asked so many times it really needed to be here.)

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, plug the included debug adapter into the charging USB-C port and switch the white switch to its "ON" position to bypass eMMC/SPI boot. This tries to boot from SD, and if no SD is inserted, enters Maskrom mode.

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

==== Performing USB Tethering with a KaiOS phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use a KaiOS phone for mobile Internet use with your PineTab2.

You'll need:

* A KaiOS phone
* A USB OTG adapter (hama #00200311 tested)
* Your device’s charging cable
* Some knowledge of your KaiOS phone

Do the following in order:

* Plug the device into the PineTab2 using the USB cable and a USB OTG adapter
* On your KaiOS phone, open settings (specifics from here may vary on version)
* Navigate to "Network & Connectivity"
* Navigate to "Internet Sharing"
* Select "USB" and select On under USB tethering (Note: This option will be greyed out unless connected to the PineTab2)

You should now see a new network interface on the PineTab2 and it should show a wired connection icon.

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

2023-06-09T20:14:22Z

Andree: /* Releases */

[[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. Similarly packaged RISC-V tablet is [[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 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.

== 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 PineTab2 ships with ''Danctnix Arch Linux ARM''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

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

File:Pinetab2-side.jpeg

2023-06-09T18:21:20Z

Andree: Side ports of the tablet

== Summary ==
Side ports of the tablet
== Licensing ==
{{cc-by-sa-4.0}}

File:Pinetab2-pogo.jpeg

2023-06-09T18:20:27Z

Andree: Pogo (usb) pins of pinetab2

== Summary ==
Pogo (usb) pins of pinetab2
== Licensing ==
{{cc-by-sa-4.0}}

File:Pinetab2-front.jpeg

2023-06-09T18:19:09Z

Andree: Front side and keyboard

== Summary ==
Front side and keyboard
== Licensing ==
{{cc-by-sa-4.0}}

PineTab2

2023-06-09T18:05:08Z

Andree: /* Specifications */ eMMC spec

[[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. Similarly packaged RISC-V tablet is [[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 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.

== 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 PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

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

2023-06-09T17:55:47Z

Andree: /* Board information, schematics and certifications */ fcc

[[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. Similarly packaged RISC-V tablet is [[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 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.

== 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 PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** 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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* [https://fccid.io/2A8NB-PINETAB2 FCC: 2A8NB-PINETAB2]

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

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

2023-06-09T11:20:43Z

Andree: /* Arch Linux ARM */ +uboot

This page contains a list of all available releases and tools for the [[PineTab2]] in alphabetical order.

== Linux ==

=== Arch Linux ARM ===

(Unofficial) Arch Linux ARM maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]). This includes [https://github.com/dreemurrs-embedded/Pine64-Arch/blob/master/PKGBUILDS/pine64/uboot-pinetab2/PKGBUILD uboot].

Download:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz

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

Notes:

* Currently ships without a Wi-Fi and Bluetooth driver
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)
* [https://forum.pine64.org/showthread.php?tid=18313 screen rotated 90°, workaround possible]

== BSD ==

[[Category:Rockchip RK3566]]

PineTab2 Releases

2023-06-09T08:47:24Z

Andree: 90°login fix

This page contains a list of all available releases and tools for the [[PineTab2]] in alphabetical order.

== Linux ==

=== Arch Linux ARM ===

(Unofficial) Arch Linux ARM maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

Download:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz

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

Notes:

* Currently ships without a Wi-Fi and Bluetooth driver
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)
* [https://forum.pine64.org/showthread.php?tid=18313 screen rotated 90°, workaround possible]

== BSD ==

[[Category:Rockchip RK3566]]

User:Andree

2023-06-09T08:31:37Z

Andree: Created page with "* [https://wiki.t-firefly.com/en/ROC-RK3566-PC/driver_camera.html rk3566 camera DTS example, inspiration for pinetab2]"

* [https://wiki.t-firefly.com/en/ROC-RK3566-PC/driver_camera.html rk3566 camera DTS example, inspiration for pinetab2]

PineTab2

2023-06-09T06:29:50Z

Andree: audio features / microphone

[[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. Similarly packaged RISC-V tablet is [[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 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.

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

=== Releases ===

The PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** 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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* Available soon

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

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

2023-06-09T06:23:03Z

Andree:

[[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. Similarly packaged RISC-V tablet is [[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 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.

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

=== Releases ===

The PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** 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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 3.5mm audio jack
** 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)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* Available soon

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

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

2023-06-09T06:21:51Z

Andree: /* Specifications */ usb clarification

[[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. Similarly packaged RISC-V tablet is [[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 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.

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

=== Releases ===

The PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** 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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0 (top, host mode only; power output up to 680mA)
** 1x USB-C 2.0 (bottom, device mode by default; power input)
** 1x MicroHDMI
** 1x 3.5mm audio jack
** 1x 5 pin (USB) Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* Available soon

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

However, if you just need to run a few simple android apps, you might want to have a look at [https://docs.waydro.id/usage/install-on-desktops Waydroid] which can be installed on Arch Linux ARM using the following command: <code>sudo pacman -S waydroid</code>

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

Yes. Widevine, using the `widevine-aarch64` package in the AUR is working, and was demonstrated on the PineTab2 using Paramount+ and Disney+. Install it (`yay -S widevine-aarch64`), run the included register script to get Firefox to recognize it, and it should start working.

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

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

2023-06-07T15:19:56Z

Andree: /* Linux */ +manjaro

PineTab2

2023-06-07T07:24:20Z

Andree: add known bugs section

[[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. Similarly packaged RISC-V tablet is [[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 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.

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

=== Releases ===

The PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

Picture of the USB UART inserted into the PineTab2. The switch to disable the eMMC and SPI is located on the top right of the image:

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. 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.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** 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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0
** 1x USB-C 2.0
** 1x MicroHDMI
** 1x 3.5mm audio jack
** 1x 5 pin Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* Available soon

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

No, there are no Widevine binaries included in the image the PineTab2 ships with. They need to be taken from ChromeOS and probably patched https://gist.github.com/DavidBuchanan314/c6b97add51b97e4c3ee95dc890f9e3c8

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

==== Performing USB Tethering with an iPhone ====

Prerequisite:

On the iPhone make sure that Settings -> Personal Hotspot -> Allow others to join is turned on.

# Use an Lightning (Apple) to USB-C (Pinetab2) cable to connect the devices.
# In the Pinetab make sure to use the USB-C port next to the volume keys.
# Once the cable is connected open your iPhone.
# You will see a request to trust the new device. Trust it.
# Confirm by typing in your Apple Device PIN

This should be it. The Pinetab2 will show you the new device and the network connects to `Wired connection 1`

== Known bugs ==
* [https://wiki.archlinux.org/title/SDDM#KDE_Plasma_Wayland_hangs_on_shutdown_and_reboot system hangs on reboot/shutdown] (SDDM bug, workaround possible)

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

2023-06-06T05:39:24Z

Andree: /* Development efforts */ links to Segfault's repos

[[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. Similarly packaged RISC-V tablet is [[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 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.

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

=== Releases ===

The PineTab2 ships with ''Danctnix Arch Linux''. The factory image can be found here:

* https://echo.danctnix.org:7269/danctnix-factory-image-20230527.img.xz (1.5 GB)

{{Info|The factory image is flashed to a microSD card and it will overwrite the eMMC installation after booting.}}

There are currently no further releases. Future releases for the PineTab2 will be listed under [[PineTab2 Releases]]. Your contributions are wanted!

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

{{Hint|'''Note regarding the boot order:''' The internal memory (eMMC) has a higher boot priority than the microSD card. In some cases it can be required to bypass the boot order, for example if the installation on the eMMC is corrupted.}}

[[File:PineTab2 USB UARTv2.jpg|600px]]

{{Hint|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. Set the ''SD BOOT MASKROM'' switch on the adapter to ''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 ''OFF'' again when the factory image is started, otherwise the factory image won't find the eMMC.}}

It should now boot the new operating system from the microSD card.

== Keyboard ==

When connecting the keyboard to the Pinetab2 ensure that the camera and the golden pogo pin connectors are correctly aligned.

Change the backlight with '''Pinekey - Ctrl-Right'''.

== Specifications ==

[[File:RK3566_icon.png|right]]
* '''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
** 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
** Bluetooth
* '''I/O:'''
** 1x USB-C 3.0
** 1x USB-C 2.0
** 1x MicroHDMI
** 1x 3.5mm audio jack
** 1x 5 pin Pogo connector for keyboard
** (PCIe on PCB as a flat flex ribbon connector, no room for M.2 NVMe drives in case)
* '''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
* '''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 ===

* The display panel driver is in PineTab2's kernel fork, and needs to be submitted to upstream.
* The [https://gitlab.com/TuxThePenguin0/bes2600 BES2600 Wi-Fi driver] needs porting/major cleanup. This is a priority, but for now, you can [[#Performing USB Tethering with an Android Phone|USB tether a phone]] or [[#Selecting a USB WIFI Adapter|use a supported WI-FI dongle]].
* The BES2600 Bluetooth driver needs to be implemented.
* The Camera driver needs to be written.
* Suspend does not currently work due to a driver issue. Suspend is disabled in the factory image for your protection. 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 in the USB-C port furthest away from the power button
* 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>

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

PineTab2 certifications:
* Available soon

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

== Frequently Asked Questions ==

=== Does the Tablet support a Pen? ===

No, adding a digitiser for pen inputs would make the price too high.

=== Can I run Android on it? ===

Theoretically yes, practically there's little chance anyone wants to make a well-supported Android build for this device. If you're looking for an Android tablet, buy any mainstream tablet, you'll get better value for your money.

=== Is there SPI Flash? ===

Unclear. The schematic shows a 128Mbit SPI flash chip, but it's possible that production models won't have it populated. Update this section once we've determined this.

=== My only Development Experience is Visual Basic Macros in Excel and Redstone in Minecraft, should I buy this? ===

At this stage, probably not, unless you're happy with a tablet that has a buggy Wi-Fi driver and no camera controller driver.

=== How does the Tablet compare to a Pinebook Pro? ===

It's slower, as it is intended to be a successor to the PineTab1, not the Pinebook Pro. It'll still handle web browsing, video playback and documents fine though.

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

=== Does PineTab2 play back DRM'd Content such as Netflix? ===

No, there are no Widevine binaries included in the image the PineTab2 ships with. They need to be taken from ChromeOS and probably patched https://gist.github.com/DavidBuchanan314/c6b97add51b97e4c3ee95dc890f9e3c8

== How-to ==

=== Putting the Device into Maskrom Mode ===

To recover from a bad eMMC/SPI flash, it seems you can make the bootrom enter the USB recovery mode by applying a low(?) signal to the SSTX1_P or SSTX2_P pin of the USB2-only Type-C connector (the one that does UART.)

=== Networking using USB ===

Until the internal BES2600 WIFI has a stable driver, the community suggests that you connect using USB. This section summarizes the more detailed information in [[File:PineTab2_USB_Guide.pdf]], which covers connecting via [[#Performing USB Tethering with an Android Phone|a tethered Android phone]], [[#Selecting a USB WIFI Adapter|a suitable USB WIFI adapter]], a wired USB Ethernet adapter, and a tethered iOS device.

==== Selecting a USB WIFI Adapter ====

Insert a supported WIFI dongle in the upper USB port, using a USB-C to USB-A adapter as necessary. As a general rule, single state adapters are recommended. Even better, select one from this list: https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

If you must use a multi-state adapter and it isn't recognized by the kernel, you can try ejecting the device. This ''should'' force it back into adapter mode. If this does not work, you can try installing [https://man.archlinux.org/man/usb_modeswitch.1.en usb_modeswitch] to troubleshoot. You will need to temporarily use another method to get internet (such as phone tethering below) or load the package on an SD card to install it.

==== Performing USB Tethering with an Android Phone ====

This guide simply describes HOW to undertake this option. The user is responsible for ensuring that their wireless plan permits such use, and for any fees incurred.

You can use an Android phone as a network adapter.

You'll need:

* An Android phone
* A USB OTG adapter (USB-C to USB-C may work, not tested)
* Some knowledge of your variation of Android

Do the following in order:

* Plug in the device to the PineTab2 using the USB cable and a USB OTG adapter
* On your android phone, open the settings app (specifics from here may vary on version)
** Navigate to "Network & Internet"
** Navigate to "Hotspot & Tethering"
** Tap on "USB Tethering"

You should now see a new network interface on the PineTab2.

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

PineTab-V

2023-05-17T10:08:50Z

Andree: board info

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

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

The PineTab-V is shipped without an operating system pre-installed.

== Releases ==

There are currently no 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
* Selfie Camera: Single 2MP

Sound:

* Loudspeaker: Yes, stereo
* 3.5mm jack with mic: Yes, stereo

Communication:

* WLAN: Wi-Fi 802.11 ax/ac/b/g/n, dual-band, hotspot
* Bluetooth: 5.2, A2DP

Features:

* USB port: 1x USB 3.0 port (front side 3.0, rear side 2.0), 1x USB Type-C 2.0 port (also use as charging and debug port)
* USB 2.0 docking port
* HD Video out

Battery:

* Removable Li-Po 6000mAh battery
* Charging: 15W – 5V 3A

== Board information, schematics and certifications ==
[[File:PineTab-V-PCB.jpg|thumb|right|PineTab-V Board]]
PineTab-V mainboard schematic:
* TODO

PineTab_V certifications:
* TODO

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

File:PineTab-V-PCB.jpg

2023-05-17T10:08:04Z

Andree: PineTab-V PCB from https://www.pine64.org/2023/04/10/pinetab-v-and-pinetab2-launch/

== Summary ==
PineTab-V PCB from https://www.pine64.org/2023/04/10/pinetab-v-and-pinetab2-launch/

PineTab2

2023-05-17T10:02:53Z

Andree: /* Board information, schematics and certifications */

PineTab2

2023-05-17T10:01:32Z

Andree:

PineTab-V

2023-05-17T10:00:50Z

Andree:

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

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

The PineTab-V is shipped without an operating system pre-installed.

== Releases ==

There are currently no 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
* Selfie Camera: Single 2MP

Sound:

* Loudspeaker: Yes, stereo
* 3.5mm jack with mic: Yes, stereo

Communication:

* WLAN: Wi-Fi 802.11 ax/ac/b/g/n, dual-band, hotspot
* Bluetooth: 5.2, A2DP

Features:

* USB port: 1x USB 3.0 port (front side 3.0, rear side 2.0), 1x USB Type-C 2.0 port (also use as charging and debug port)
* USB 2.0 docking port
* HD Video out

Battery:

* Removable Li-Po 6000mAh battery
* Charging: 15W – 5V 3A

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

File:PPineTab2-pcb.jpg

2023-05-17T09:59:48Z

Andree: PineTab2 board from https://www.pine64.org/2023/04/10/pinetab-v-and-pinetab2-launch/

== Summary ==
PineTab2 board from https://www.pine64.org/2023/04/10/pinetab-v-and-pinetab2-launch/

PineTab

2023-05-17T09:57:00Z

Andree:

[[File:Pinetab.jpg|400px|thumb|right|The PineTab]]

The '''PineTab''' is a 10" tablet created by PINE64. The PineTab is similar in both form, function and underlying ARM64 architecture to the original 11.6″ Pinebook. It is powered by the same quad-core ARM Cortex A53 64-Bit Processor used in our popular PINE A64 Single Board Computer. The optional keyboard and trackpad – which doubles-up as a screen cover – effectively converts the PineTab into a petite on-the-go laptop with a touch screen functionality. It runs numerous mainline Linux distributions as well as *BSD and Android.

Superseded by [[PineTab2]].
== Revisions ==

* Developer Edition - development version sent to roughly 100 developers. Close to the Early Adopter Edition, but with a different display panel
* [[PineTab/Early-Adopter|Early Adopter Edition]] - the first hardware revision of the PineTab

[[File:PineTabBoard.jpeg|400px|thumb|right|The insides of the PineTab]]

[[File:PineTab_Board.jpg|thumb|right|Pinetab Board]]

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''SOC:''' Allwinner A64 Quad Core
* '''CPU:''' 4x ARM A53 1.152GHz
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network:'''
** WiFi (802.11b/g/n, 2.4GHz only)
** Bluetooth 2.1
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Display:'''
** '''Size:''' 10.1 inches (257mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1280x800, 16:10 ratio 
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''' Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed all except for postmarketOS have working builds.

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|right|80px]]

Unofficial '''Arch Linux ARM''' with Phosh as the UI selection, maintained by the DanctNIX community.

Download:
* The latest image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases here]

-----

=== Manjaro ARM ===
[[File:Manjaro-logo.svg|right|80px]]

'''Manjaro''' is a Linux based alternative operating system with no adverts or licensing fees, it respects user privacy and gives them full control over their hardware. The PineTab "Early Adopter" edition is currently the only device supported by Manjaro ARM.

Download:
* Images with several different environments, including Phosh and Plasma, are available for the "Dev" pre-release can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]
* Images for the Early Adopter version can be downloaded [https://github.com/manjaro-arm/pinetab-images/releases here].

Both Beta releases and weekly unstable builds for Phosh and Plasma Mobile can be found there.

-----

=== Mobian ===
[[File:Debian-logo.png|right|80px]]

'''Mobian''' is a project providing Debian images for mobile devices.

Download:
* PineTab images can be downloaded [https://images.mobian.org/pinetab/ here]. The password is '''1234'''

-----

=== postmarketOS ===
[[File:PostmarketOS_logo.png|right|80px]]

'''postmarketOS''' extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.

It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4 and more). As of writing, official images are provided with Phosh and Plasma Mobile. The official images come in two flavors, either as demo image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt your installation
* install from the SD card to eMMC

Getting postmarketOS for the PineTab:
* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab)#Installation Flashing instructions]
* Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>

-----

=== Sailfish OS ===

[[File:SailfishOS logo.png|right|80px]]

You can get '''SailfishOS''' on your with the flash-it script, which will write an image on a SD card. https://github.com/sailfish-on-dontbeevil/flash-it

There is a forum discussion with further information.

http://forum.pine64.org/showthread.php?tid=11850

Many things are still broken but Bluetooth, Audio, Rotation and Keyboard are working.

-----

=== UBPorts ===
[[File:Ubports-logo.png|right|80px]]

The '''UBPorts Ubuntu Touch''' is what was preinstalled on the PineTab Early Adopters batch.

It can update itself in System Settings, and also a jenkins daily build can be downloaded at this updated address for the latest daily image:

https://ci.ubports.com/job/rootfs/job/rootfs-pinetab-systemimage/

The last stable builds are also listed and appear to be updated every few weeks.

It should be noted that as of 20th January the latest stable/release candidate and development builds still lacked Bluetooth, Rotation and had the same issues with online accounts etc

Online accounts access have a fix for Google accounts here https://github.com/rubencarneiro/account-plugins/releases

There are however significant updates to the original PineTab image (without the issues above)

The old image appears to be deprecated here
[https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

In the event that WiFi fails to connect, the USB port can be used with an appropriate dongle to connect for internet using ethernet cable.

== Installation instructions ==
For instructions on how to install the operating systems to the eMMC or microSD card see [[PinePhone Installation Instructions]]. The information is almost the same for the PineTab, as it is a very similar device. Do not try to use the PinePhone images though, use the PineTab images linked above.

For details see the [[Getting started]] article.

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start: Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot.

=== Power Off While Charging ===

When plugging your Pinetab into a charger, it automatically powers on. Use the above "Reset" instruction (holding the power button in for several seconds) to turn it off. This will allow your Pinetab to charge without being powered on.

=== Display rotated 90° on Arch ARM ===
With the following command you can turn the display to landscape:

echo 1 | sudo tee /sys/class/graphics/fbcon/rotate

This command does not persist a reboot.

== Assembly and disassembly ==

Be very careful here. It is not a 'pop off' cover design.
Special care should be directed to AVOID anything that may appear to cause a "bend" in screen.

Gently use fingernails (or if you have one, plastic pry), starting in the very middle location for each side (saving keyboard connector latch over area (bottom side) for the very last removal step).

Work your way from the inner middle on each side, slowly. Slide gently towards the direction of each corner (saving the lifting of actual corners themselves for the second to last step)). Careful not to break thin speaker wires that line the outside of the inner case.

The very last opening piece should be the "latch over" (where the keyboard pins connect).

KEEP IN MIND: The main key here is to avoid any potential "bend" of the screen. We save the corners until after working on the middle of each side to reduce pressure on the screen.

Do not force anything. If it is not coming off with gentle effort, you are likely doing something wrong (try another side middle).

== Board information, schematics and certifications ==

PineTab mainboard schematic:
* [https://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
* [https://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
* [https://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]

PineTab keyboard schematic:
* PineTab keyboard and Pinebook (Pro) keyboard using same controller and from same engineering source
* [https://files.pine64.org/doc/PineTab/Pinetab%20HB092A%20Keyboard%20Schematic.pdf PineTab Keyboard Schematic]
* [https://files.pine64.org/doc/PineTab/HB092_0884232458_Hynitron_PTP_20200514_662905_Linux_US_BackLight_CRC_175057F5.hex PineTab keyboard firmware code]
* [https://files.pine64.org/doc/PineTab/SH68F83V2.0.pdf PineTab Keyboard Controller Datasheet]

PineTab certifications:
* [https://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
* [https://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]
* [https://files.pine64.org/doc/cert/PINETAB%20ROHS%20TEST%20REPORT.pdf PineTab ROHS Test Report]

== Datasheets for components and peripherals ==
Allwinner A64 SoC information:
* [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
* [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
* [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

X-Powers AXP803 PMU (Power Management Unit) information:
* [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem 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/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB SanDisk eMMC Datasheet]

CMOS camera module information:
* [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
* [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

LCD touch screen panel information:
* [https://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
* [https://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

Lithium battery information:
* N/A

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

== External Links ==
* [https://pine64.com/product/pinetab-10-1-linux-tablet/ The PineTab on the Pine64 store]
* [https://forum.pine64.org/forumdisplay.php?fid=140 The PineTab section of the Pine64 forums]
* [https://forum.pine64.org/showthread.php?tid=11401 Comments on back cover removal on forums]
* [https://forum.pine64.org/showthread.php?tid=13118 Demonstration Video: Pinetab back cover removal on forums]

[[Category:PineTab]] [[Category:Allwinner A64]]