Prod update

.wordlist.txt

@@ -4667,7 +4667,7 @@ Sommelier
 chromeos
 linuxcontainers
 XPS
-NIC's 
+NIC’s
 offlines
 passthrough
 SLOs
@@ -4722,4 +4722,94 @@ ATtestation
 CoCo
 procedureS
 NIC’s
+httpbin
+proxying
+OpenBMC
+PoC
+PoCs
+evb
+ipmitool
+openbmc
+poc
+IPMI
+integrators
+KCS
+PLDM
+MCTP
+Redfish
+hyperscalers
+BMCs
+OEM
+NetFn
+RDv
+CSSv
+penBmc
+BMC's
+socat
+ZooKeeper
+IRQs
+IRQS
+Friedt
+namespaces
+atlascli
+benchmarkDB
+cursorTest
+replset
+testCollection
+Namespaces
+mongotop
+Mongotop
+baselineDB
+ef
+netstat
+tulnp
+mongostat
+arw
+conn
+getmore
+qrw
+vsize
+conn
+WiredTiger
+GLE
+getLastError
+createIndex
+getMore
+getmore
+RoT
+lkvm
+JMH
+jmh
+UseG
+Xmx
+Xms
+JavaServer
+servlets
+RMSNorm
+RoPE
+FFN
+ukernel
+libstreamline
+prefill
+OpenCL
+subgraphs
+threadpool
+worksize
+Zhilong
+Denoiser
+RGGB
+denoised
+YGGV
+Mohamad
+Najem
+kata
+svl
+svzero
+anf
+DynamIQ
+Zena
+learnt
+lof
+BalenaOS
+balenaCloud
 

assets/contributors.csv

@@ -100,4 +100,5 @@ Ann Cheng,Arm,anncheng-arm,hello-ann,,
 Fidel Makatia Omusilibwa,,,,,
 Ker Liu,,,,,
 Rui Chang,,,,,
-
+Alejandro Martinez Vicente,Arm,,,,
+Mohamad Najem,Arm,,,,

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

@@ -27,7 +27,7 @@ armips:
 tools_software_languages:
     - Python
     - Docker
-    - ROS2
+    - ROS 2
     - DDS
 operatingsystems:
     - Linux

content/learning-paths/automotive/system76-auto/_index.md

@@ -22,7 +22,6 @@ armips:
 operatingsystems:
     - Linux
 tools_software_languages:
-    - Automotive
 
 further_reading:
     - resource:

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

@@ -0,0 +1,54 @@
+---
+title: Debug Arm Zena CSS Reference Software Stack with Arm Development Studio
+
+draft: true
+cascade:
+    draft: true
+
+minutes_to_complete: 60
+
+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
+
+prerequisites:
+    - Ubuntu 22.04 host machine
+    - 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: Performance and Architecture
+armips:
+    - Cortex-A
+    - Cortex-R
+operatingsystems:
+    - Linux
+tools_software_languages:
+    - Arm Development Studio
+    - Arm Zena CSS
+
+
+further_reading:
+    - resource:
+        title: Arm Zena Compute System (CSS)
+        link: https://developer.arm.com/Compute%20Subsystems/Arm%20Zena%20Compute%20Subsystem
+        type: website
+    - resource:
+        title: Arm Development Studio
+        link: https://developer.arm.com/Tools%20and%20Software/Arm%20Development%20Studio
+        type: website
+
+
+### FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 1                       # _index.md always has weight of 1 to order correctly
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+learning_path_main_page: "yes"  # This should be surfaced when looking for related content. Only set for _index.md of learning path content.
+---

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

@@ -0,0 +1,63 @@
+---
+# User change
+title: "Model Configuration"
+
+weight: 4 # 1 is first, 2 is second, etc.
+
+# Do not modify these elements
+layout: "learningpathall"
+---
+
+# Debug Configuration
+
+Arm Development Studio requires a `Debug Configuration` of the target that it will connect to.
+
+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 they are also summarized below.
+
+## Launch FVP
+
+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
+
+Debug Configurations are stored in a configuration database. You must first create a local database in which to store the configuration.
+
+Navigate to `File` > `New` > `Other`, and then select `Configuration Database` > `Configuration Database` from the drop-down list.
+
+Click `Next`. Give the Database a name, and click `Finish`.
+
+## Debug Configuration
+
+Navigate to the same wizard as above, and select `Model Configuration`.
+
+Click `Next`, and you will be prompted to select the above `Configuration Database`. Click `Next` again, and you will be prompted to select a Model Interface.
+
+Select `Iris` from the pulldown, and click `Next`.
+
+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.
+
+The debugger is now aware of the FVP and you are ready to debug.

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

@@ -0,0 +1,75 @@
+---
+# User change
+title: "Debug Connections"
+
+weight: 5 # 1 is first, 2 is second, etc.
+
+# Do not modify these elements
+layout: "learningpathall"
+---
+
+## Debug Connections
+
+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.
+
+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
+
+First, create a project to store these connections (`.launch` files) in.
+
+Select `File` > `New...` > `Project` > `General` > `Project`, and give it a meaningful name (`Connections`).
+
+### RSE (Cortex-M55)
+
+Runtime Security Engine (RSE) is based on [Cortex-M55](https://developer.arm.com/Processors/Cortex-M55) core and is a security subsystem fulfilling the role of Root of Trust.
+
+Select `File` > `New` > `Model Connection`.
+
+{{% notice Note %}}
+You can also use `File` > `New` > `Other` > `Arm Debugger` > `Model Connection`, or
+
+`Create a debug connection...` shortcut in the `Debug Control` pane.
+{{% /notice %}}
+
+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 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 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`.
+
+{{% notice Note %}}
+`127.0.0.1` is the same as `localhost`, that is the same host machine as is running the FVP.
+
+It is also possible to connect to a remote host by specifying appropriate IP address, and launching FVP with the `-A` option.
+
+`7100` is the default port number. You may need to change this if necessary.
+{{% /notice %}}
+
+Click `Apply` to save the connection information, and `Close`. Observe that `RSE.launch` is created inside the `Connections` project.
+
+### Safety Island (Cortex-R82AE)
+
+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 drop-down.
+
+{{% notice %}}
+For convenience you can copy-and-paste `RSE.launch` as `SI.launch` and just modify the CPU.
+{{% /notice %}}
+
+### Primary Compute (Cortex-A720AE)
+
+The Primary Compute consists of four processor clusters to run a rich OS such as Linux. Each processor cluster includes four [Cortex-A720AE](https://developer.arm.com/Processors/Cortex-A720AE) cores and a [DSU-120AE](https://developer.arm.com/Processors/DSU-120AE) DynamIQ Shared Unit.
+
+The application processors will be debugged in an SMP configuration with Linux Kernel awareness.
+
+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 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

@@ -0,0 +1,56 @@
+---
+# User change
+title: "Launch FVP"
+
+weight: 3 # 1 is first, 2 is second, etc.
+
+# Do not modify these elements
+layout: "learningpathall"
+---
+
+## Launch FVP
+
+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"
+```
+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.
+
+You will use the following. See output of `FVP_RD_Aspen --help` for full list and explanation. Options are case-sensitive.
+
+| Option                | Alias    | Notes                                         |
+|---------------------- |--------- |---------------------------------------------- |
+| `--iris-server`       | `-I`     | Start Iris Debug Server                       |
+| `--iris-port`         |          | Specify a port number (default = `7100`)      |
+| `--run`               | `-R`     | Run simulation when debug server started      |
+| `--iris-allow-remote` | `-A`     | Allow remote connections (if different hosts) |
+
+### Launch FVP with additional options
+
+To launch the FVP with additional options, modify the above command by adding `--` and then the options.
+
+For example, to launch the model with the debug server and hold at the initial reset condition:
+
+```command
+kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100"
+```
+
+To launch the model and start running (so that it can start to boot up):
+
+```command
+kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100 --run"
+```
+
+To launch the model so that remote hosts can access it (not recommended if not needed), using options aliases:
+
+```command
+kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- -I -A --iris-port 7100"
+```
+
+{{% notice Note %}}
+It is recommended to specify the port number used even if it is the default as that must match the debug connection setting (see later).
+{{% /notice %}}