Updates based on JT feedback

Author: RonanSynnottArm

content/learning-paths/automotive/zenacssdebug/config.md

@@ -23,6 +23,14 @@ As per previous section, launch FVP with the Iris server enabled:
 ```command
 kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100"
 ```
+or if connecting to the FVP remotely:
+
+```command
+kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100 -A"
+```
+{{% notice Note %}}
+A local connection is assumed for the remainder of this learning path.
+{{% /notice %}}
 
 ## Configuration Database
 
@@ -44,6 +52,10 @@ You will then be prompted to locate the model to connect to.
 
 Select `Browse for model running on local host`. The FVP will be detected and interrogated by the debugger.
 
+{{% notice Note %}}
+Use `Connect to model running on either local or remote host` if connecting remotely.
+{{% /notice %}}
+
 A `model.mdf` file will be created that identifies all CPUs within the FVP.
 
 You can change the `Manufacturer Name` and `Platform Name` to something more meaningful (such as `Arm` and `Zena_CSS_FVP`), then `Save`, and `Import` into the configuration database.

content/learning-paths/automotive/zenacssdebug/connect.md

@@ -32,7 +32,7 @@ You can also use `File` > `New` > `Other` > `Arm Debugger` > `Model Connection`,
 `Create a debug connection...` shortcut in the `Debug Control` pane.
 {{% /notice %}}
 
-Specify a connection name (`RSE`), and associate with the above project. Click `Next`.
+Specify a connection name (`RSE`), and associate with the above `Connections` project. Click `Next`.
 
 Locate the FVP based on the name you gave it previously (`Zena_CSS_FVP`). The text filter can help locate easily.
 

content/learning-paths/automotive/zenacssdebug/primarycompute.md

@@ -26,11 +26,12 @@ For example the processors start in `EL3` and moves to `EL2N` when the Linux ker
 
 ``` text
 stop
-
 add-symbol-file /arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/trusted-firmware-a/2.11.0+git/image/firmware/bl2.elf EL3:0x0
-
 tbreak bl2_entrypoint
 ```
+{{% notice Note %}}
+Exact paths may differ for your set up.
+{{% /notice %}}
 
 Run the code to the `bl2_entrypoint` and you can debug as expected.
 
@@ -40,9 +41,7 @@ To make use of the OS awareness, disconnect `Primary_init` and connect to `Prima
 
 ``` text
 stop
-
 add-symbol-file /arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/linux-yocto/6.6.54+git/linux-fvp_rd_aspen-standard-build/vmlinux EL2N:0x0
-
 set substitute-path /usr/src/kernel/ /arm-auto-solutions/build/tmp_baremetal/work-shared/fvp-rd-aspen/kernel-source/
 ```
 Run the FVP until the OS prompt appears.

content/learning-paths/automotive/zenacssdebug/rse.md

@@ -30,7 +30,6 @@ The FVP will start and emit various informational messages. Once initialized you
 ```output
 ...
 Info: RD_Aspen: RD_Aspen.css.smb.rse_flashloader: FlashLoader: Saved 64MB to file '~/arm-auto-solutions/build/tmp_baremetal/deploy/images/fvp-rd-aspen/rse-flash-image.img'
-
 Info: RD_Aspen: RD_Aspen.ros.flash_loader: FlashLoader: Saved 128MB to file '~/arm-auto-solutions/build/tmp_baremetal/deploy/images/fvp-rd-aspen/ap-flash-image.img'
 ```
 
@@ -40,7 +39,7 @@ Note that execution has not started.
 
 Using the `RSE` connection created in the previous section, connect the debugger to the FVP. Observe that the processor is stopped before the first instruction has been executed.
 
-In fact, the FVP is configured to have the vector table (`VTOR_S`) start at `0x11000000`, and it you inspect memory at that address the vector table will be populated. However no debug information is visible. Debug information must be loaded.
+In fact, the FVP is configured to have the vector table (`VTOR_S`) start at `0x11000000`, and if you inspect memory at that address the vector table will be populated. However no debug information is visible. Debug information must be loaded.
 
 In the `Debug Pane`, select `Load...` from the pane menu, and select `Add Symbols file`.
 
@@ -73,11 +72,8 @@ It is recommended to have an explicit `stop` command as symbols cannot be loaded
 
 ``` text
 stop
-
 add-symbol-file /arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/trusted-firmware-m/2.1.0/build/bin/bl1_1.axf
-
 set substitute-path /usr/src/debug/trusted-firmware-m/2.1.0/ /arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/trusted-firmware-m/2.1.0/git/tfm/
-
 stepi
 ```
 ![Debugger pane](debugger_commands.png)

content/learning-paths/automotive/zenacssdebug/safetyisland.md

@@ -23,14 +23,15 @@ Set up the `SI` connection in a similar way as the `RSE` connection. Use the fol
 
 ``` text
 stop
-
 add-symbol-file /arm-auto-solutions/build/tmp_baremetal/deploy/images/fvp-rd-aspen/si0_ramfw.elf
-
 set substitute-path /usr/src/debug/scp-firmware/2.14.0/ /arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/scp-firmware/2.14.0/git/
-
 b arch_exception_reset
 ```
 
+{{% notice Note %}}
+Exact paths may differ for your set up.
+{{% /notice %}}
+
 ### Start execution
 
 Select the `RSE` connection in the `Debug Control` pane, and start execution (this will be unavailable in the `SI` connection, as that is currently powered down).