WIP

Signed-off-by: Daniil Klimuk <[email protected]>

Author: DaniilKl

docs/guides/optee/optee-on-rk3566.md

@@ -0,0 +1,3 @@
+# OPTEE on RK3566
+
+

docs/guides/optee/optee.md

@@ -0,0 +1,3 @@
+# OPTEE
+
+

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)

docs/supported-targets/targets.md

@@ -5,3 +5,7 @@ This section contains a list of supported vendors and their targets.
 ## Radxa
 
 * [Radxa CM3 System on Module](./radxa-cm3.md).
+
+## PINE64
+
+* [Quartz64 Model A SBC](./quartz64-a.md)

mkdocs.yml

@@ -72,10 +72,15 @@ nav:
       - 'Targets': supported-targets/targets.md
       - 'Radxa':
           - 'Radxa CM3': supported-targets/radxa-cm3.md
+      - 'PINE64':
+          - 'Quartz64 Model A': supported-targets/quartz64-a.md
   - 'Guides':
       - 'Managing packages': guides/managing-packages.md
       - 'Managing layers': guides/managing-layers.md
       - 'Secure Boot Verification': guides/secure-boot/secure-boot-verification.md
+      - 'OPTEE':
+        - 'OPTEE': guides/optee/optee.md
+        - 'OPTEE on RK3566': guides/optee/optee-on-rk3566.md
   - 'Development Process':
       - 'Standard Release Process': development-process/standard-release-process.md
   - 'FAQ': faq.md