docs: Move all odroid H4+ files from unified to variants

Signed-off-by: Filip Gołaś <filip.golas@3mdeb.com>

docs/unified/hardkernel/building-manual.md → docs/variants/hardkernel_odroid_h4_plus/building-manual.md

@@ -22,14 +22,18 @@ then follow the steps below:
 
 === "Odroid H4+"
 
-    1. Checkout to the device's branch:
+    1. To build a specific version checkout to the version's tag.
+    Skip this step otherwise.
+
             ```bash
             cd coreboot
-            git checkout hardkernel_odroid_h4/release
+            git checkout hardkernel_odroid_h4_<version>
             ```
+        For example
 
-    To build a specific version replace `hardkernel_odroid_h4/release` with
-    `hardkernel_odroid_h4_v0.9.x` where `x` is the version number.
+        ```bash
+        git checkout hardkernel_odroid_h4_v0.9.0-rc2
+        ```
 
     2. Checkout submodules:
 
@@ -43,4 +47,4 @@ then follow the steps below:
     ```
 
     The resulting coreboot image will be placed in the coreboot directory as
-    `hardkernel_odroid_h4.rom`.
+    `hardkernel_odroid_h4_<version>.rom`.

docs/variants/hardkernel_odroid_h4_plus/hardware-matrix.md

@@ -5,7 +5,7 @@
 This document describes the hardware configuration used for validation of
 Dasharo on the Hardkernel ODROID H4+.
 
-## MinnowBoard Turbot Quad Core
+## Hardkernel ODROID H4+
 
 | Component                      | Description                                 |
 |--------------------------------|---------------------------------------------|

docs/variants/hardkernel_odroid_h4_plus/recovery.md

@@ -0,0 +1,67 @@
+# Recovery
+
+## Intro
+
+The following documentation describes the process of recovering hardware from
+the brick state using an [RTE](../../transparent-validation/rte/introduction.md)
+and Dasharo open-source firmware.
+
+## Prerequisites
+
+* [Prepared RTE](../../transparent-validation/rte/v1.1.0/quick-start-guide.md)
+* 6x female-female wire cables
+
+## Connections
+
+To prepare the stand for flashing follow the steps described in
+the [Generic test stand setup](../../unified-test-documentation/generic-testing-stand-setup.md#detailed-description-of-the-process)
+
+## Firmware flashing
+
+To flash firmware follow the steps described below:
+
+1. Login to RTE via `ssh` or `minicom`.
+2. Turn on the platform by connecting the power supply.
+3. Wait at least 5 seconds.
+4. Turn off the platform by using the power button.
+5. Wait at least 3 seconds.
+6. Set the proper state of the SPI by using the following commands on RTE:
+
+    ```bash
+    # set SPI Vcc to 3.3V
+    echo 1 > /sys/class/gpio/gpio405/value
+    # SPI Vcc on
+    echo 1 > /sys/class/gpio/gpio406/value
+    # SPI lines ON
+    echo 1 > /sys/class/gpio/gpio404/value
+    ```
+
+7. Wait at least 2 seconds.
+8. Disconnect the power supply from the platform.
+9. Wait at least 2 seconds.
+10. Check if the flash chip is connected properly
+
+    ```bash
+    flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=16000
+    ```
+
+11. Flash the platform by using the following command:
+
+    ```bash
+    flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=16000 -w [path_to_binary]
+    ```
+
+    > Flashing with flashrom takes about 1 minute.
+
+12. Change back the state of the SPI by using the following commands:
+
+    ```bash
+    echo 0 > /sys/class/gpio/gpio404/value
+    echo 0 > /sys/class/gpio/gpio405/value
+    echo 0 > /sys/class/gpio/gpio406/value
+    ```
+
+13. Turn on the platform by connecting the power supply.
+
+The first boot of the platform after proceeding with the above procedure can
+take much longer than normal.