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

Signed-off-by: Filip Gołaś <[email protected]>

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

@@ -20,16 +20,20 @@ To build Dasharo firmware image, first clone the coreboot repository:
     ```
 then follow the steps below:
 
-=== "Odroid H4+"
+=== "Odroid H4"
+
+    1. To build a specific version checkout to the version's tag.
+    Skip this step otherwise.
 
-    1. Checkout to the device's branch:
             ```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/unified/hardkernel/firmware-update.md → docs/variants/hardkernel_odroid_h4/firmware-update.md

@@ -34,10 +34,8 @@ medium lock and Secure Boot:
 The settings of all the above options can be restored after a firmware
 update.
 
-=== "ODROID H4+"
+## Updating Dasharo
 
-    ## Updating Dasharo
-
-    ```bash
-    flashrom -p internal -w hardkernel_odroid_h4_v<version>.rom --fmap -i bios
-    ```
+```bash
+flashrom -p internal -w hardkernel_odroid_h4_v<version>.rom --fmap -i bios
+```

docs/variants/hardkernel_odroid_h4_plus/hardware-matrix.md → docs/variants/hardkernel_odroid_h4/hardware-matrix.md

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

docs/unified/hardkernel/initial-deployment.md → docs/variants/hardkernel_odroid_h4/initial-deployment.md

@@ -24,13 +24,11 @@ your own backup should be the last resort.
 
 ## Flashing Dasharo
 
-=== "ODROID H4+"
+To flash Dasharo on the platform, execute the following command - replace `[path]`
+with the path to the Dasharo image you want to flash, e.g. `hardkernel_odroid_h4_v0.9.0.rom`.
 
-    To flash Dasharo on the platform, execute the following command - replace `[path]`
-    with the path to the Dasharo image you want to flash, e.g. `hardkernel_odroid_h4_v0.9.0.rom`.
-
-    ```bash
-    sudo flashrom -p internal -w [path] --ifd -i bios
-    ```
+```bash
+sudo flashrom -p internal -w [path] --ifd -i bios
+```
 
-    After successful operation reboot the platform.
+After successful operation reboot the platform.

docs/variants/hardkernel_odroid_h4/overview.md

@@ -0,0 +1,6 @@
+# Overview
+
+=== "Hardkernel ODROID H4"
+    - [Releases](../../variants/hardkernel_odroid_h4/releases.md)
+    - [Hardware Configuration Matrix](../../variants/hardkernel_odroid_h4/hardware-matrix.md)
+    - [Test Matrix](./test-matrix.md#hardkernel-odroid-h4)

docs/variants/hardkernel_odroid_h4/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.

docs/variants/hardkernel_odroid_h4_plus/releases.md → docs/variants/hardkernel_odroid_h4/releases.md

@@ -1,14 +1,14 @@
 # Dasharo compatible with Hardkernel ODROID H4+
 
 Following Release Notes describe status of Open Source Firmware development for
-Hardkernel ODROID H4+
+Hardkernel ODROID H4
 
 For details about our release process please read
 [Dasharo Standard Release Process](../../dev-proc/standard-release-process.md).
 
 <center>
 
-[Subscribe to Hardkernel ODROID H4+ Dasharo Release Newsletter]
+[Subscribe to Hardkernel ODROID H4 Dasharo Release Newsletter]
 [newsletter]{ .md-button .md-button--primary .center }
 
 </center>