Merge pull request #2299 from pareenaverma/content_review

Zena CSS ArmDS Tech review

Author: pareenaverma

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

@@ -4,36 +4,35 @@ title: Debug Arm Zena CSS Reference Software Stack with Arm Development Studio
 draft: true
 cascade:
     draft: true
-    
-description: Learn how to set up a debug environment for Arm Zena CSS Reference Software Stack
 
 minutes_to_complete: 60
 
-who_is_this_for: This topic is for software developers who wish to use Arm Development Studio to explore and debug the Arm Zena CSS Reference Software Stack.
+who_is_this_for: This is an introductory topic for software developers who wish to use Arm Development Studio to explore and debug the Arm Zena CSS Reference Software Stack.
 
 learning_objectives: 
     - Set up debug configuration for the Arm Zena CSS FVP
     - Debug Runtime Security Engine (RSE) from boot time
     - Debug Safety Island (SI)
     - Debug Linux OS on Primary Compute cores
-##    - Debug Linux application
 
 prerequisites:
     - Ubuntu 22.04 host machine
-    - Arm Development Studio 2024.1 (or later) and an appropriate license
+    - You will need [Arm Development Studio 2024.1 (or later)](/install-guides/armds) and an appropriate license
     - A basic understanding of the Arm Zena CSS software stack and Arm processors
 
 author: Ronan Synnott
 
 ### Tags
 skilllevels: Introductory
-subjects: 
+subjects: Performance and Architecture
 armips:
-    - Arm Zena CSS
+    - Cortex-A
+    - Cortex-R
 operatingsystems:
     - Linux
 tools_software_languages:
     - Arm Development Studio
+    - Arm Zena CSS
 
 
 further_reading:

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

@@ -12,9 +12,9 @@ layout: "learningpathall"
 
 Arm Development Studio requires a `Debug Configuration` of the target that it will connect to.
 
-As of 2025.0, there is no such configuration provided 'out-of-the-box' for the Zena CSS FVP. However creating such a configuration is straight forward.
+As of Arm Development Studio version 2025.0, there is no such configuration provided 'out-of-the-box' for the Zena CSS FVP. However creating such a configuration is straight forward.
 
-See the Arm Development Studio [Getting Started Guide](https://developer.arm.com/documentation/101469/latest/Migrating-from-DS-5-to-Arm-Development-Studio/Connect-to-new-or-custom-models) for full instructions, but summarized below.
+See the Arm Development Studio [Getting Started Guide](https://developer.arm.com/documentation/101469/latest/Migrating-from-DS-5-to-Arm-Development-Studio/Connect-to-new-or-custom-models) for full instructions, but they are also summarized below.
 
 ## Launch FVP
 
@@ -38,7 +38,7 @@ Debug Configurations are stored in a configuration database. You must first crea
 
 Navigate to `File` > `New` > `Other`, and then select `Configuration Database` > `Configuration Database` from the drop-down list.
 
-Click `Next`. Give the Database a meaningful name, and click `Finish`.
+Click `Next`. Give the Database a name, and click `Finish`.
 
 ## Debug Configuration
 

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

@@ -10,13 +10,13 @@ layout: "learningpathall"
 
 ## Debug Connections
 
-You are now ready to create debug connections for each of the sub-systems within Zena CSS. This section will create the connections, which will be subsequently enhanced in the following section. You may prefer to fully set up one such connection before moving to others.
+You are now ready to create debug connections for each of the sub-systems within Zena CSS. In this section you will create the connections, which will be subsequently enhanced in the following section. You may prefer to fully set up one such connection before moving to others.
 
-Development Studio has full support for Heterogeneous systems such as Zena CSS, and so you can connect to all processors simultaneously.
+Arm Development Studio has full support for Heterogeneous systems such as Zena CSS, and so you can connect to all processors simultaneously.
 
 ### Debug connection project
 
-It may be sensible to create a project to store these connections (`.launch` files) in.
+First, create a project to store these connections (`.launch` files) in.
 
 Select `File` > `New...` > `Project` > `General` > `Project`, and give it a meaningful name (`Connections`).
 
@@ -34,11 +34,11 @@ You can also use `File` > `New` > `Other` > `Arm Debugger` > `Model Connection`,
 
 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.
+Locate the FVP based on the name you gave it previously (`Zena_CSS_FVP`). The text filter can help you locate it easily.
 
 You will then be presented with the `Edit configuration` pane. In the `Connection` tab, scroll down to locate `Bare Metal Debug` > `Arm_Cortex-M55`.
 
-As we shall be later launching the FVP with the software stack loaded, select `Connect to an already running model`.
+As you will be later launching the FVP with the software stack loaded, select `Connect to an already running model`.
 
 Assuming the same host will be running both the FVP and the debugger, specify the `Connection address` as the default `127.0.0.1:7100`.
 
@@ -56,10 +56,10 @@ Click `Apply` to save the connection information, and `Close`. Observe that `RSE
 
 The Safety Island is a subsystem based on [Cortex-R82AE](https://developer.arm.com/Processors/Cortex-R82AE) core. The software running on the Safety Island is responsible for power, clock and CMN control.
 
-The procedure to create this connection is very similar to the above, other than to select `Bare Metal Debug` > `Arm_Cortex-R82AE` from the pull down.
+The procedure to create this connection is very similar to the above, other than to select `Bare Metal Debug` > `Arm_Cortex-R82AE` from the drop-down.
 
 {{% notice %}}
-For convenience you can copy-and-paste `RSE.launch` as `SI.launch` and simply modify the CPU.
+For convenience you can copy-and-paste `RSE.launch` as `SI.launch` and just modify the CPU.
 {{% /notice %}}
 
 ### Primary Compute (Cortex-A720AE)
@@ -68,8 +68,8 @@ The Primary Compute consists of four processor clusters to run a rich OS such as
 
 The application processors will be debugged in an SMP configuration with Linux Kernel awareness.
 
-As above, create `Primary_init.launch` connection and scroll to `Bare Metal Debug` > `ARM_Cortex-A720AE_0`. This will connect to just CPU0, leaving the other CPUs free to run.
+As shown above, create `Primary_init.launch` connection and scroll to `Bare Metal Debug` > `ARM_Cortex-A720AE_0`. This will connect to just CPU0, leaving the other CPUs free to run.
 
-To debug the Linux kernel we can make use of the [OS awareness](https://developer.arm.com/documentation/101470/latest/Debugging-Embedded-Systems/About-OS-awareness) feature of the Arm Debugger.
+To debug the Linux kernel you can make use of the [OS awareness](https://developer.arm.com/documentation/101470/latest/Debugging-Embedded-Systems/About-OS-awareness) feature of the Arm Debugger.
 
 Create `Primary_Linux.launch` connection and scroll to `Linux Kernel Debug` > `ARM_Cortex-A720AEx16 SMP Cluster 1`. This will connect to all 16 `Cortex-A720AE` processors present in the FVP, though only cores 0-3 are used.

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

@@ -10,17 +10,17 @@ layout: "learningpathall"
 
 ## Launch FVP
 
-From the [documentation](https://arm-auto-solutions.docs.arm.com/en/v2.0/rd-aspen/user_guide/reproduce.html#run-the-fvp) the default command to launch the FVP (within the virtual environment) with the software stack loaded is:
+You can now launch the FVP within the virtual environment with the software stack loaded:
 
 ```command
 kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose"
 ```
-
-It is sensible to continue to use this method to launch the FVP whilst debugging. However this command as shown does not enable the Iris debug server inside the model, and so will not be debuggable.
+Refer to the [documentation](https://arm-auto-solutions.docs.arm.com/en/v2.0/rd-aspen/user_guide/reproduce.html#run-the-fvp) for more details.
+While you can continue to use this method to launch the FVP whilst debugging, this command does not enable the Iris debug server inside the model, and so will not be debuggable.
 
 Additional command options are necessary.
 
-We will use the following. See output of `FVP_RD_Aspen --help` for full list and explanation. Options are case-sensitive.
+You will use the following. See output of `FVP_RD_Aspen --help` for full list and explanation. Options are case-sensitive.
 
 | Option                | Alias    | Notes                                         |
 |---------------------- |--------- |---------------------------------------------- |

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

@@ -12,9 +12,9 @@ layout: "learningpathall"
 
 The Primary Compute application processors (`Cortex-A720AE`) are the final processors to be enabled.
 
-As before we can connect whilst powered down and monitor the point that they are enabled.
+As before, you can connect whilst powered down and monitor the point that they are enabled.
 
-You can debug the initialization code and/or the final Linux Operating System (OS) threads.
+You can debug the initialization code and the final Linux Operating System (OS) threads.
 
 ### Connect debugger to target
 
@@ -37,7 +37,7 @@ Run the code to the `bl2_entrypoint` and you can debug as expected.
 
 ### Debug Linux kernel modules
 
-To make use of the OS awareness, disconnect `Primary_init` and connect to `Primary_Linux` as created previously. Load the symbols from `vmlinux` image.
+To make use of the OS awareness feature, disconnect `Primary_init` and connect to `Primary_Linux` as created previously. Load the symbols from the `vmlinux` image.
 
 ``` text
 stop
@@ -47,7 +47,7 @@ set substitute-path /usr/src/kernel/ /arm-auto-solutions/build/tmp_baremetal/wor
 Run the FVP until the OS prompt appears.
 
 {{% notice %}}
-If only interested in kernel debug, modify the launch command for the FVP to include `--run` to start execution immediately.
+If you are only interested in kernel debug, modify the launch command for the FVP to include `--run` to start execution immediately.
 
 ``` command
 kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100 --run"
@@ -67,3 +67,5 @@ WARNING(ROS60): Could not enable OS support as the OS does not appear to be init
 ```
 may be emitted if the OS is not booted when you connect. It can safely be ignored.
 {{% /notice %}}
+
+You have successfully learnt how to use Arm Development Studio to explore and debug the Arm Zena CSS Reference Software Stack.

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

@@ -25,7 +25,7 @@ To debug from reset, launch the FVP with the Iris server but do not run. This wi
 ```command
 kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100"
 ```
-The FVP will start and emit various informational messages. Once initialized you should see something similar to:
+The FVP will start and generate various informational messages. Once initialized you should see something similar to:
 
 ```output
 ...

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

@@ -19,7 +19,7 @@ If necessary, restart the FVP in the reset state as before, and reconnect `RSE`.
 kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100"
 ```
 
-Set up the `SI` connection in a similar way as the `RSE` connection. Use the following commands in the `Debugger` pane. This will load debug symbols and performing the necessary path substitution. You can then set a breakpoint on the entry point of the `SI` code, `arch_exception_reset`.
+Set up the `SI` connection in a similar way as the `RSE` connection. Use the following commands in the `Debugger` pane. This will load debug symbols and perform the necessary path substitution. You can then set a breakpoint on the entry of the `SI` code, `arch_exception_reset`.
 
 ``` text
 stop
@@ -44,6 +44,8 @@ The `RSE` code will run until the point that the `SI` is enabled. This is reflec
 
 #### Full output log
 
+The full output lof is shown here for your reference:
+
 ``` output
 Trying ::1...
 Trying 127.0.0.1...

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

@@ -22,12 +22,12 @@ For more information, see [Arm Zena Compute Subsystem (CSS)](https://developer.a
 
 ## Build software stack
 
-The steps to download and build the software stack are described in the [User Guide](https://arm-auto-solutions.docs.arm.com/en/v2.0/rd-aspen/user_guide/reproduce.html).
+Follow the steps to download and build the software stack in the [User Guide](https://arm-auto-solutions.docs.arm.com/en/v2.0/rd-aspen/user_guide/reproduce.html).
 
 The default `Arm Automotive Solutions Demo` build is used.
 
 {{% notice Note %}}
-This learning path is focused on **debugging** the software stack only.
+The focus of this Learning Path is to demonstrate the **debug** of the software stack.
 {{% /notice %}}
 
 ## Verify correct build and execution
@@ -58,16 +58,16 @@ For legacy reasons the FVP is named is `FVP_RD_Aspen`.
 
 Arm Development Studio is a software development solution with support of multicore debug for Arm CPUs. It provides the earliest support for the latest processors.
 
-The CPUs implemented within Arm Zena CSS are supported by Arm Development Studio 2024.0 and later, though 2024.1 or later is recommended for appropriate Linux OS support. At time of writing the latest version available is 2025.0, and that is the version used for screenshots etc in this learning path.
+The CPUs implemented within Arm Zena CSS are supported by Arm Development Studio 2024.0 and later, though 2024.1 or later is recommended for appropriate Linux OS support. At time of writing the latest version available is 2025.0, and that is the version used for this learning path.
 
 For more information see [Arm Development Studio](https://developer.arm.com/Tools%20and%20Software/Arm%20Development%20Studio).
 
 Arm Development Studio is a commercial, license managed, product. For installation and set up instructions, see this [Install Guide](/install-guides/armds/).
 
-Launch the IDE. We recommend creating a new workspace folder.
+Launch the IDE. It is recommended to create a new workspace folder.
 
 If prompted by the launcher (this is disabled by default) create a new folder there, else select `File` > `Switch Workspace` > `Other...`.
 
-{{% notice %}}
+{{% notice Note %}}
 To enable this prompt by default, navigate to `Window` > `Preferences` > `General` > `Startup and Shutdown` > `Workspaces`, and enable `Prompt for workspace on startup`.
 {{% /notice %}}