diff --git a/doc/README-bbb.md b/doc/README-bbb.md
index e82d522..831337c 100644
--- a/doc/README-bbb.md
+++ b/doc/README-bbb.md
@@ -89,8 +89,11 @@ These prerequisites are valid for Linux as well as Windows hosts.
    arm-linux-gnueabihf-gcc --version
    ```
 
-4. Set up a sysroot folder on the local host machine. Make sure the SSH connection to
-   the BBB is working without issues. Then perform the following steps
+4. Set up a sysroot folder on the local host machine. It is recommended that you download a prepared
+   sysroot form [here](https://www.dropbox.com/sh/5k6kwgx3j88dv99/AABI22dRYrMdfGZyzbbIZdOQa?dl=0)
+   and start from there instead of  performing the clone process yourself. This is because some
+   necessary steps like converting absolute symlinks to relative symlinks were already performed.
+   If you want to do this, perform the following steps:
 
    ```sh
    cd $HOME
@@ -185,10 +188,13 @@ These prerequisites are valid for Linux as well as Windows hosts.
    arm-linux-gnueabihf-gcc --version
    ``` 
 
-4. Set up a sysroot folder on the local host machine. Make sure the SSH connection to
-   the BBB is working without issues. Then perform the following steps
+4. Set up a sysroot folder on the local host machine. It is recommended that you download a prepared
+   sysroot form [here](https://www.dropbox.com/sh/5k6kwgx3j88dv99/AABI22dRYrMdfGZyzbbIZdOQa?dl=0)
+   and start from there instead of  performing the clone process yourself. This is because some
+   necessary steps like converting absolute symlinks to relative symlinks were already performed.
+   If you want to do this, perform the following steps:
 
-   ```sh
+   ```sh 
    cd /c/Users/<UserName>
    mkdir beaglebone
    cd beaglebone
@@ -290,7 +296,13 @@ and running it on the BBB via command line. Navigate into the `fsfw_example` fol
    The `BBB` folder also contains template shell files which can be `source`d
    to quickly set up the environmental variables if you want to keep the system path clean.
 
-3. Run the binary to test it
+3. Build the binary
+
+   ```sh
+   cmake --build . -j
+   ```
+
+4. Run the binary to test it
 
    ```sh
    scp fsfw_example <username>@beaglebone.local:/home/fsfw_example
diff --git a/doc/README-rpi.md b/doc/README-rpi.md
index 7afe8d3..ecdfd31 100644
--- a/doc/README-rpi.md
+++ b/doc/README-rpi.md
@@ -114,8 +114,11 @@ cross-compile a toolchain yourself by following the steps in the
    arm-linux-gnueabihf-gcc --version
    ``` 
 
-2. Set up a sysroot folder on the local host machine. Make sure the SSH connection to
-   the Raspberry Pi is working without issues. Then perform the following steps
+2. Set up a sysroot folder on the local host machine. It is recommended that you download a prepared
+   sysroot form [here](https://www.dropbox.com/sh/47vfp0r4kgnanpy/AAASZpbcuMD34S-G0BVXz5SKa?dl=0)
+   and start from there instead of performing the clone process yourself. This is because some
+   necessary steps like converting absolute symlinks to relative symlinks were already performed.
+   If you want to do this yourself, perform the following steps.
 
    ```sh
    cd ~
@@ -208,8 +211,11 @@ cross-compile a toolchain yourself by following the steps in the
    arm-linux-gnueabihf-gcc --version
    ``` 
 
-4. Set up a sysroot folder on the local host machine. Make sure the SSH connection to
-   the Raspberry Pi is working without issues. Then perform the following steps
+4. Set up a sysroot folder on the local host machine. It is recommended that you download a prepared
+   sysroot form [here](https://www.dropbox.com/sh/47vfp0r4kgnanpy/AAASZpbcuMD34S-G0BVXz5SKa?dl=0)
+   and start from there instead of performing the clone process yourself. This is because some
+   necessary steps like converting absolute symlinks to relative symlinks were already performed.
+   If you want to do this yourself, perform the following steps.
 
    ```sh
    cd /c/Users/<UserName>
@@ -317,7 +323,13 @@ Navigate into the `fsfw_example` folder first.
    The `RPi` folder also contains template shell files which can be `source`d
    to quickly set up the environmental variables if you want to keep the system path clean.
 
-3. Run the binary to test it
+3. Build the binary
+
+   ```sh
+   cmake --build . -j
+   ```
+
+4. Run the binary to test it
 
    ```sh
    scp fsfw_example pi@raspberrypi.local:/home/pi/fsfw_example