WIP Technical Review

Author: annietllnd

content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/intro.md

@@ -23,7 +23,7 @@ Several pre-built Armv8-A FVPs can be downloaded for free from the [Arm Ecosyste
 - Infrastructure
 - IoT
 
-A popular model is the **AEMv8-A Base Platform RevC**, which supports Armv8.7 and Armv9-A. The [Arm reference software stack](https://gitlab.arm.com/arm-reference-solutions/arm-reference-solutions-docs/-/blob/master/docs/aemfvp-a/user-guide.rst) is designed for this model.
+A popular model is the **AEMv8-A Base Platform RevC**, which supports Armv8.7 and Armv9-A. The [Arm reference software stack](https://gitlab.arm.com/arm-reference-solutions/arm-reference-solutions-docs/-/blob/master/docs/aemfvp-a/user-guide.rst) is designed for this model. In this Learning Path, you will use the Armv-A Base Platform RevC FVP to get started.
 
 ### CPU-Specific Arm Base FVPs
 Other FVPs target specific CPU types and come pre-configured with a fixed number of cores. These are often called **CPU FVPs**.
@@ -39,8 +39,44 @@ To use these, request access via [support@arm.com](mailto:support@arm.com).
 ### Setting Up Your Environment
 This Learning Path uses the [Arm reference software stack](https://gitlab.arm.com/arm-reference-solutions/arm-reference-solutions-docs/-/blob/master/docs/aemfvp-a/user-guide.rst).
 
-To get started:
-1. Follow the software user guide to download the stack.
-2. Set up the required toolchain and environment variables.
+Create a workspace directory to use as a base for this Learning Path.
 
-Once configured, you’ll be ready to run and debug Linux on your selected Arm FVP model.
+```
+mkdir linux-on-fvp-workspace && cd linux-on-fvp-workspace
+export WORKSPACE=$PWD
+```
+
+Follow the software user guide to download the stack, up until the point of enabling the network. You can use the workspace directory you just created, instead of creating an additional one. This includes downloading the FVP, installing some dependencies and using a pre-built docker image to set up the packages needed. Install some additional dependencies, and add the FVP binary to your `PATH` environment variable.
+
+```
+sudo apt update
+sudo apt install bridge-utils net-tools mtools
+export PATH=$WORKSPACE/Base_RevC_AEMvA_pkg/models/Linux64_armv8l_GCC-9.3
+:$PATH
+```
+
+To verify the process, you should be able to run the `build-test-busybox.sh` script.
+
+```
+cd $WORKSPACE
+docker_run ./build-scripts/aemfvp-a/build-test-busybox.sh -p aemfvp-a all
+```
+
+The build will take a few minutes.
+
+{{% notice Note %}}
+If you're running into compatibility issues with OpenSSL, you have to install a separate version:
+
+```bash
+cd $WORKSPACE
+wget https://www.openssl.org/source/openssl-1.1.1.tar.gz
+tar -xvzf openssl-1.1.1.tar.gz
+cd openssl-1.1.1/
+./Configure linux-aarch64 --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib
+make -j$(($(nproc)+1))
+sudo make install
+export LD_LIBRARY_PATH=/usr/local/ssl/lib:${LD_LIBRARY_PATH}
+```
+{{% /notice %}}
+
+Once configured, you’ll be ready to run and debug Linux on your selected Arm FVP model. Move on to the next section.

content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/modify.md

@@ -8,7 +8,7 @@ layout: learningpathall
 
 ## Modify the Device Tree for CPU FVPs
 
-To run Linux on Arm CPU FVPs, you need to adjust the device tree to match the hardware features of these platforms. This involves removing unsupported nodes (like SMMU (System Memory Management Unit)and PCI (Peripheral Component Interconnect)) and ensuring CPU affinity values are set correctly.
+To run Linux on Arm CPU FVPs, you need to adjust the device tree to match the hardware features of these platforms. This involves removing unsupported nodes - like SMMU (System Memory Management Unit) and PCI (Peripheral Component Interconnect) - and ensuring CPU affinity values are set correctly.
 
 ### Step 1: Remove PCI and SMMU Nodes
 
@@ -35,7 +35,7 @@ Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
 Each FVP model uses specific CPU affinity values. If these don’t match what’s in the device tree, some CPU cores won’t boot.
 1.	Find the correct affinities:
 ```bash
-FVP_Base_Cortex-A55x4 -l | grep pctl.CPU-affinities
+FVP_Base_RevC-2xAEMvA -l | grep pctl.CPU-affinities
 ```
 Example output:
 

content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/steps.md

@@ -23,32 +23,25 @@ lib/cpus/aarch64/cortex_a53.S
 ... etc.
 ```
 
-## Why you need this
-
-If the firmware is built without proper cpu_ops, you’ll hit an assertion failure like:
+If the firmware is built without proper `cpu_ops`, you’ll hit an assertion failure like:
 
 ```output
 ASSERT: File lib/cpus/aarch64/cpu_helpers.S Line 00035
 ```
 
 This means the required CPU operation routines are missing from the build.
 
-## Step-by-Step: Add TF-A Build Flags
+## Add TF-A Build Flags
 
 To include the correct `cpu_ops`, you need to set TF-A build options depending on the CPU.
 
-### Example: A55 CPU FVP
 
-Add the following line to your TF-A build script:
+Add the following line to your TF-A build script to update the options for the the AEMv8-A Base Platform RevC:
 
-```output
+```bash
 ARM_TF_BUILD_FLAGS="$ARM_TF_BUILD_FLAGS HW_ASSISTED_COHERENCY=1 USE_COHERENT_MEM=0"
 ```
 
-### Example: A78 CPU FVP
-```output
-ARM_TF_BUILD_FLAGS="$ARM_TF_BUILD_FLAGS HW_ASSISTED_COHERENCY=1 USE_COHERENT_MEM=0 CTX_INCLUDE_AARCH32_REGS=0"
-```
 {{% notice Note %}}
 USE_COHERENT_MEM=1 cannot be used with HW_ASSISTED_COHERENCY=1.
 {{% /notice %}}