Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 70d79ba

Browse files
committedMar 25, 2025
docs: supported-targets: quartz64-a: add
Signed-off-by: Daniil Klimuk <[email protected]>
1 parent 5aa0c7e commit 70d79ba

File tree

3 files changed

+53
-0
lines changed

3 files changed

+53
-0
lines changed
 

‎docs/supported-targets/quartz64-a.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
# Quartz64 Model A
2+
3+
## Description and resources
4+
5+
The [Quartz64 Model A](https://pine64.org/devices/quartz64_model_a/) is a SBC
6+
based on Rockchip RK3566 and produced by PINE64.
7+
8+
Additional resources for the board:
9+
10+
* [PINE64
11+
documentation;](https://pine64.org/documentation/Quartz64/Further_information/Schematics_and_certifications/)
12+
* [PINE64 Wiki](https://wiki.pine64.org/wiki/Quartz64)
13+
* [Rockchip Wiki: partitions map;](https://opensource.rock-chips.com/wiki_Partitions)
14+
* [Rockchip Wiki: boot flow.](https://opensource.rock-chips.com/wiki_Boot_option#Boot_introduce)
15+
16+
## Serial port access (Zarhus OS debug console)
17+
18+
Numerous types of software can be used to communicate via serial ports. On a
19+
host machine with Linux-based OS it can be `minicom`, Windows users can access
20+
that with [PuTTY](https://www.putty.org/).
21+
22+
There are only two parameters that depend not only on hardware but on software
23+
as well: baudrate and serial port number. In case of Quartz64 Model A port -
24+
Zarhus OS gives access to console via serial port 2 with baudrate `1.5 Mbps`, so
25+
you can connect to the console by connecting the UART adapter to pins `8`, `10`
26+
and `10` of
27+
[`CON40`](https://files.pine64.org/doc/quartz64/Quartz64_model-A_schematic_v2.0_20210427.pdf)
28+
29+
And use following command on your host Linux distribution:
30+
31+
```bash
32+
$ minicom -b 1500000 -D /dev/ttyUSBX
33+
```
34+
35+
Where instead of `/dev/ttyUSBX` there should be the name of your UART adapter
36+
under your host Linux distribution.
37+
38+
## Zarhus OS image building and flashing
39+
40+
For building steps check the [generic Zarhus OS building
41+
guide.](../getting-started/building.md)
42+
43+
For flashing steps check the [generic Zarhus OS SD card flashing
44+
guide.](../getting-started/flashing.md)
45+
46+
You can verify the booted image by follwoing [generic Zarhus OS image
47+
verification.](../getting-started/verification.md)

‎docs/supported-targets/targets.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,7 @@ This section contains a list of supported vendors and their targets.
55
## Radxa
66

77
* [Radxa CM3 System on Module](./radxa-cm3.md).
8+
9+
## PINE64
10+
11+
* [Quartz64 Model A SBC](./quartz64-a.md)

‎mkdocs.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,8 @@ nav:
7272
- 'Targets': supported-targets/targets.md
7373
- 'Radxa':
7474
- 'Radxa CM3': supported-targets/radxa-cm3.md
75+
- 'PINE64':
76+
- 'Quartz64 Model A': supported-targets/quartz64-a.md
7577
- 'Guides':
7678
- 'Managing packages': guides/managing-packages.md
7779
- 'Managing layers': guides/managing-layers.md

0 commit comments

Comments
 (0)
Please sign in to comment.