From c6fa4d76ca672e1658fd021db307fcc57b0b1c21 Mon Sep 17 00:00:00 2001 From: Daniil Klimuk Date: Tue, 28 Jan 2025 12:05:00 +0100 Subject: [PATCH] docs: supported-targets: quartz64-a: add Signed-off-by: Daniil Klimuk --- docs/supported-targets/quartz64-a.md | 47 ++++++++++++++++++++++++++++ docs/supported-targets/targets.md | 4 +++ mkdocs.yml | 2 ++ 3 files changed, 53 insertions(+) create mode 100644 docs/supported-targets/quartz64-a.md diff --git a/docs/supported-targets/quartz64-a.md b/docs/supported-targets/quartz64-a.md new file mode 100644 index 0000000..c7a9b02 --- /dev/null +++ b/docs/supported-targets/quartz64-a.md @@ -0,0 +1,47 @@ +# Quartz64 Model A + +## Description and resources + +The [Quartz64 Model A](https://pine64.org/devices/quartz64_model_a/) is a SBC +based on Rockchip RK3566 and produced by PINE64. + +Additional resources for the board: + +* [PINE64 +documentation;](https://pine64.org/documentation/Quartz64/Further_information/Schematics_and_certifications/) +* [PINE64 Wiki](https://wiki.pine64.org/wiki/Quartz64) +* [Rockchip Wiki: partitions map;](https://opensource.rock-chips.com/wiki_Partitions) +* [Rockchip Wiki: boot flow.](https://opensource.rock-chips.com/wiki_Boot_option#Boot_introduce) + +## Serial port access (Zarhus OS debug console) + +Numerous types of software can be used to communicate via serial ports. On a +host machine with Linux-based OS it can be `minicom`, Windows users can access +that with [PuTTY](https://www.putty.org/). + +There are only two parameters that depend not only on hardware but on software +as well: baudrate and serial port number. In case of Quartz64 Model A port - +Zarhus OS gives access to console via serial port 2 with baudrate `1.5 Mbps`, so +you can connect to the console by connecting the UART adapter to pins `8`, `10` +and `10` of +[`CON40`](https://files.pine64.org/doc/quartz64/Quartz64_model-A_schematic_v2.0_20210427.pdf) + +And use following command on your host Linux distribution: + +```bash +$ minicom -b 1500000 -D /dev/ttyUSBX +``` + +Where instead of `/dev/ttyUSBX` there should be the name of your UART adapter +under your host Linux distribution. + +## Zarhus OS image building and flashing + +For building steps check the [generic Zarhus OS building +guide.](../getting-started/building.md) + +For flashing steps check the [generic Zarhus OS SD card flashing +guide.](../getting-started/flashing.md) + +You can verify the booted image by follwoing [generic Zarhus OS image +verification.](../getting-started/verification.md) diff --git a/docs/supported-targets/targets.md b/docs/supported-targets/targets.md index 19d1e4a..892891a 100644 --- a/docs/supported-targets/targets.md +++ b/docs/supported-targets/targets.md @@ -9,3 +9,7 @@ This section contains a list of supported vendors and their targets. ## Raspberry Pi * [Raspberry Pi 4](./rpi4.md) + +## PINE64 + +* [Quartz64 Model A SBC](./quartz64-a.md) diff --git a/mkdocs.yml b/mkdocs.yml index e06615b..321a378 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -75,6 +75,8 @@ nav: - 'Radxa CM3': supported-targets/radxa-cm3.md - 'Raspberry Pi': - 'Raspberry Pi 4': supported-targets/rpi4.md + - 'PINE64': + - 'Quartz64 Model A': supported-targets/quartz64-a.md - 'Guides': - 'Managing packages': guides/managing-packages.md - 'Managing layers': guides/managing-layers.md