Difference between revisions of "QuartzPro64 Development"

From PINE64
Jump to navigation Jump to search
(add a photo of the development board)
(add more photos)
Line 89: Line 89:


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


== Cooler ==
== Cooler ==
Line 105: Line 107:


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


* Soldered on 64 GB FORESEE eMMC chip, it comes pre-flashed with some Android (you'll even get a brief bit of HDMI output)
* Soldered on 64 GB FORESEE eMMC chip, it comes pre-flashed with some Android (you'll even get a brief bit of HDMI output)

Revision as of 11:04, 4 May 2022

The QuartzPro64 development board

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

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

Upstreaming Status

Function Status Component Notes
Video Output Needs porting VOP2 The video output IP on the RK3588 should mostly be the same as the one on the RK356x, but the chip specific stuff will need to be integrated into the vop2 driver (once it's merged)
Video Input Needs porting
3D Acceleration In review[1] Upstream Mesa panfrost Initial support in Mesa as of 22.2[2], changes specific to this SoC may be needed to both kernel and Mesa.
Video Decode Needs writing GStreamer only, no ffmpeg[3] hantro using v4l2-requests VDPU121 handling 1080p60 H.263/MPEG-4, MPEG-1 and MPEG-2
Needs writing rkvdec2 using v4l2-requests VDPU346 handling 8K60 H.265, H.264, VP9 and AVS
Needs writing rkdjpeg using v4l2-requests VDPU720 handling JPEG
Needs writing ? using v4l2-requests VDPU981 handling 4K60 AV1
Video Encode Needs writing GStreamer only JPEG on VEPU121 Driver already exists, only minor changes needed. Very unfinished GStreamer implementation, doesn't allow for e.g. controlling the quality.
Needs writing ? H.264 on VEPU580
Needs writing ? H.265 on VEPU580
Audio Needs porting rockchip-i2s-tdm Should be exactly the same as RK356x (according to the TRM), just needs compatible string copypasted over probably
CRU In review[4] clk-rk3588
SD/MMC In review[5] sdhci-of-dwcmshc
pinctrl linux-next[6] pinctrl-rockchip
GPIO In review[7] rockchip-gpio

Hardware

The SoC and RAM packages

Cooler

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

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

UART

Plug in the USB-C port labelled "DEBUG PORT" on the board, it will show up as a FT232 USB Serial adapter. Baud rate is as usual 1.5mbauds or 1500000.

Mounting Holes

Can't be bothered to take a precise measurement of all the holes right now, just use some PC standoffs and have the board sit on your desk, it's a dev board after all.

Storage

The eMMC on the dev board
  • Soldered on 64 GB FORESEE eMMC chip, it comes pre-flashed with some Android (you'll even get a brief bit of HDMI output)
  • microSD card slot
  • 2x SATA 3.0 (molex power connector for it not populated, but easy to remedy)

Resources