Production update

.github/workflows/roadmap-update.yml

@@ -171,13 +171,23 @@ jobs:
                     console.log('Start Date field not found');
                   }
                 } else if (labelName === 'publish') {
-                  const endDateFieldId = await getFieldId(projectId, 'Publish Date');
-                  if (endDateFieldId) {
-                    await updateDateField(projectId, itemId, endDateFieldId, today);
+                  // Publish Date
+                  const publishDateFieldId = await getFieldId(projectId, 'Publish Date');
+                  if (publishDateFieldId) {
+                    await updateDateField(projectId, itemId, publishDateFieldId, today);
                     console.log('Updated Publish Date to', today);
                   } else {
                     console.log('Publish Date field not found');
                   }
+
+                  // Last Reviewed Date (same as Publish Date)
+                  const lastReviewedFieldId = await getFieldId(projectId, 'Last Reviewed Date');
+                  if (lastReviewedFieldId) {
+                    await updateDateField(projectId, itemId, lastReviewedFieldId, today);
+                    console.log('Updated Last Reviewed Date to', today);
+                  } else {
+                    console.log('Last Reviewed Date field not found');
+                  }
                 } else {
                   console.log('No action taken for label:', labelName);
                 }
@@ -187,4 +197,4 @@ jobs:
               }
             }
 
-            main();
+            main();

.wordlist.txt

@@ -5055,4 +5055,104 @@ Zynq
 ZYNQ
 zypper
 ZZa
-ZZZZZ
+ZZZZZ
+Abouelseoud
+ActiveRecord
+Axion's
+Ayoub
+BeagleBone
+Bourjilat
+Buildroot's
+Bundler
+CGO
+ConfigMap
+CubeProgrammer
+DEBLOAT
+DGX
+DTC
+Disaggregated
+EP
+Espressif
+FPARMv
+FRDM
+FirewallD
+Flink's
+IDQ
+Kustomize
+LinkServer
+MCXN
+MIS
+MVC
+NVLink
+OpenOCD
+PRED
+PackageCloud
+Puncover
+PyOCD
+RemoteChannelThroughputBenchmark
+Retbleed
+SEGGER
+SVD
+Skaffold
+Skylake
+Spectre
+Superchip
+TARGETPLATFORM
+TFLOPs
+TMA
+TMAM
+UNHALTED
+VPCs
+Vmlinux
+WordCount
+YJIT
+Yahya
+backend's
+btop
+carkservice
+cartservice
+checkpointing
+cours
+dgx
+dtlb
+emailservice
+firewalld
+fopenmp
+fs
+htop
+ident
+insmod
+itlb
+ko
+kube
+loadgen
+loadgenerator
+microbenchmarks
+microcoded
+microoperation
+mknod
+mpki
+mtune
+mvn
+mychardrv
+nRF
+narrowings
+navpane
+nginx's
+nvcc
+nvtop
+oRT
+petaFLOP
+plaintext
+rbenv
+recommendationservice
+remoteRebalance
+residually
+rubyonrails
+sdcard
+smi
+spiko
+transpile
+tsc
+typescriptlang
+vmlinux

assets/contributors.csv

@@ -104,4 +104,7 @@ Alejandro Martinez Vicente,Arm,,,,
 Mohamad Najem,Arm,,,,
 Ruifeng Wang,Arm,,,,
 Zenon Zhilong Xiu,Arm,,zenon-zhilong-xiu-491bb398,,
-Zbynek Roubalik,Kedify,,,,
+Zbynek Roubalik,Kedify,,,,
+Rani Chowdary Mandepudi, Arm,,,,
+Ayoub Bourjilat,Ac6,Bourjilat,ayoub-bourjilat-a55b58165/,,https://www.ac6.fr/en/
+Yahya Abouelseoud,Arm,,,,

content/install-guides/vnc.md

@@ -9,7 +9,7 @@ additional_search_terms:
 - linux
 
 ### Estimated completion time in minutes (please use integer multiple of 5)
-minutes_to_complete: 30
+minutes_to_complete: 15
 
 author: Jason Andrews
 
@@ -29,67 +29,69 @@ multitool_install_part: false   # Set to true if a sub-page of a multi-page arti
 layout: installtoolsall         # DO NOT MODIFY. Always true for tool install articles
 ---
 
-Virtual Network Computing (VNC) is one of the common tools used to connect to a remote Linux desktop. During development it may be useful to quickly create a remote desktop on an Arm server.
+Virtual Network Computing (VNC) is one of the common tools used to connect to a remote Linux desktop. During development, it can be useful to quickly create a remote desktop on an Arm server.
 
-This section provides info about how to setup VNC on a remote Arm Linux machine.
+This guide provides information about how to set up VNC on a remote Arm Linux machine.
 
-Feel free to seek out additional VNC tutorials or add more information to this page.
-
-This installation only works on newer versions of Ubuntu and Debian. It was successfully tested on **Ubuntu 22.04** and is known to fail on **Ubuntu 20.04**.
+This installation only works on newer versions of Ubuntu and Debian. It was successfully tested on Ubuntu 22.04 and Ubuntu 24.04.
 
 ## What is VNC?
 
-VNC is a client server application. A VNC server runs on a remote machine. A VNC client runs on the local machine and connects to the remote server.
+VNC is a client-server application. A VNC server runs on a remote machine. A VNC client runs on the local machine and connects to the remote server.
 
 ### How do I install the VNC server and xfce4 desktop?
 
-To use VNC, a VNC server needs to be installed. There are multiple VNC servers which can be used. This recipe uses [TigerVNC](https://tigervnc.org/).
+To use VNC, you need to install a VNC server. There are multiple VNC servers you can use. This guide uses [TigerVNC](https://tigervnc.org/).
 
-Desktop software is also needed. There are many options for this, but using [xfce4](https://www.xfce.org/) makes for a minimal install with good performance.
+You also need desktop software. There are many options for this, but using [xfce4](https://www.xfce.org/) provides a minimal install with good performance.
 
-Install the desktop software.
+Install the desktop software:
 
 ```bash
 sudo apt-get install xfce4 xfce4-goodies xorg dbus-x11 x11-xserver-utils xfce4-terminal -y
 ```
 
-Install the VNC server.
+Install the VNC server:
 
 ```bash
 sudo apt-get install tigervnc-standalone-server tigervnc-common -y
 ```
 
 ### How do I set a VNC password?
 
-Run the password command to set a password for VNC. This is not the password for the user account, just for the VNC client to connect to the VNC server.
+Run the `vncpasswd` command to set a password for VNC. This is not the password for your user account, but for the VNC client to connect to the VNC server.
 
 ```console
 vncpasswd
 ```
 
-Remember the password for later when the client is connected.
+Remember this password for later when you connect the client.
 
 ### How do I configure the desktop startup for VNC?
 
-Create a file at `$HOME/.vnc/xstartup` with the contents:
+Create a file at `$HOME/.vnc/xstartup` with the following contents:
 
 ```console
 #!/bin/sh
 unset SESSION_MANAGER
 unset DBUS_SESSION_BUS_ADDRESS
 exec startxfce4
 ```
-Make sure the `xstartup` file has executable permission.
+Make sure the `xstartup` file has executable permissions:
+
 ```console
 chmod +x $HOME/.vnc/xstartup
 ```
 
 ### How do I set up a systemd service to manage VNC?
 
-To create a systemd service to start the VNC server create the file `/etc/systemd/system/vncserver@.service`
+To create a systemd service to start the VNC server, create the file `/etc/systemd/system/vncserver@.service`.
 
-Use sudo or root as it is located in a read-only area.
-```console
+Use `sudo` or root privileges because this file is in a system directory.
+
+If your username is not `ubuntu` change the `User` value to match your username after you create the new file. 
+
+```ini
  [Unit]
  Description=Remote desktop service (VNC)
  After=syslog.target network.target
@@ -105,9 +107,9 @@ Use sudo or root as it is located in a read-only area.
 
  [Install]
  WantedBy=multi-user.target
+```
 
- ```
-The commands below are for any Linux distribution using `systemd`.
+The following commands are for any Linux distribution that uses `systemd`.
 
 To start the VNC service:
 
@@ -129,24 +131,25 @@ sudo systemctl restart vncserver@1.service
 
 ### How do I use port forwarding via SSH to connect to VNC?
 
-The default port for the first instance of VNC is `5901`. SSH port forwarding is the best solution for accessing the Linux desktop on a cloud machine. This way no additional ports need to be opened in the security group.
+The default port for the first instance of VNC is `5901`. SSH port forwarding is the recommended solution for accessing the Linux desktop on a cloud machine. This way, no additional ports need to be opened in the security group.
 
-SSH to your remote Linux machine. Refer to [SSH](/install-guides/ssh/) for additional details.
+SSH to your remote Linux machine. See [SSH](/install-guides/ssh/) for additional details.
 
-Substitute your private key file and public IP address of the remote machine.
+Substitute your private key file and the public IP address of the remote machine in the following command:
 
 ```console
 ssh -i <private_key> -L 5901:localhost:5901 ubuntu@<public_ip_address>
 ```
 
-Once connected via SSH, use a VNC client to connect. [Download](https://sourceforge.net/projects/tigervnc/files/stable/1.12.0/) an install a TigerVNC client for your computer.
+Once connected via SSH, use a VNC client to connect. [Download](https://sourceforge.net/projects/tigervnc/files/stable/1.12.0/) and install a TigerVNC client for your computer.
+
+Open the VNC client and enter the following for the VNC server:
 
-Open the VNC client and enter the following for the VNC server.
 ```console
 localhost:5901
 ```
-You will be prompted for the password created earlier with `vncpasswd`.
+You will be prompted for the password you created earlier with `vncpasswd`.
 
-A remote Linux Desktop should appear on your local computer. Make sure to close the VNC client first and then exit the SSH connection.
+A remote Linux desktop should appear on your local computer. When you are finished, close the VNC client first and then exit the SSH connection.
 
 ![Linux desktop #center](/install-guides/_images/xfce4.png)

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

@@ -14,7 +14,7 @@ learning_objectives:
 
 prerequisites:
   - Ubuntu 22.04 host machine
-  - Arm Development Studio 2024.1 or later with a valid license - for support see the [Install Guide for ADS](/install-guides/armds) 
+  - Arm Development Studio 2024.1 or later with a valid license - for support see the [Install Guide for Arm DS](/install-guides/armds) 
   - Basic understanding of the Arm Zena CSS software stack, Armv8-A/Armv9-A cores, and Linux
 
 author: Ronan Synnott

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

@@ -46,19 +46,27 @@ Debug configurations are stored in a configuration database. Create a local data
 - Open the same wizard (**File > New > Other**), then choose **Configuration Database > Model Configuration**.
 - Click **Next**, select the **Configuration Database** you created, then click **Next**.
 - For **Model Interface**, choose **Iris**, then click **Next**.
-- Choose **Browse for model running on local host**. The debugger detects and interrogates the FVP.  
+- Choose **Browse for model running on local host**. Select your FVP and click **Finish**. The debugger detects and interrogates the FVP.  
 - If connecting remotely, choose **Connect to model running on either local or remote host** and provide the host and port.
 
+{{% notice Tip %}}
+The name of the FVP may be displayed as `RD_ASD` or other.
+
+If unsure, use the port number to identify the correct FVP.
+{{% /notice %}}
+
 Arm Development Studio generates a `model.mdf` file that enumerates all CPUs in the FVP.
 
-Optionally, update **Manufacturer Name** (for example, `Arm`) and **Platform Name** (for example, `Zena_CSS_FVP`). Then **Save** and **Import** the model into the configuration database.
+Optionally, update **Manufacturer Name** (for example, `Arm`) and **Platform Name** (for example, `Zena_CSS_FVP`).
+
+**Save** and **Import** the model into the configuration database.
 
 {{% notice Tip %}}
-If the FVP is not detected, verify the Iris server is running on the expected port (`7100` by default) and that your firewall allows local connections. For remote connections, confirm the host is reachable and the port is open.
+If the FVP is not detected, verify the Iris server is running on the expected port (`7100` by default) and that your firewall allows local connections.
+
+For remote connections, confirm the host is reachable and the port is open.
 {{% /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/primarycompute.md

@@ -25,8 +25,9 @@ For example the processors start in `EL3` and move to `EL2N` when the Linux kern
 
 ``` 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
+add-symbol-file "/arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/trusted-firmware-a/2.13.0+git/image/firmware/bl2.elf" EL3:0x0
 tbreak bl2_entrypoint
+
 ```
 
 {{% notice Note %}}
@@ -41,12 +42,20 @@ Symbol loading is Exception Level–aware. If execution changes Exception Level,
 
 ## Debug the Linux kernel with OS awareness (symmetric multiprocessing)
 
-Switch to the `Primary_Linux.launch` connection you created earlier to enable Arm Development Studio OS awareness for the Linux kernel. Load the kernel symbols and set source mapping if your kernel sources are located outside the default paths:
+{{% notice Note %}}
+OS awareness for Linux Kernel 6.12 (as used with Reference Software Stack 2.1) is not currently supported as of Arm Development Studio 2025.0.
+
+It will be supported in a future Development Studio version.
+{{% /notice %}}
+
+Disconnect `Primary_init.launch` and use the `Primary_Linux.launch` connection you created earlier to enable Arm Development Studio OS awareness for the Linux kernel.
+
+Load the kernel symbols and set source mapping if your kernel sources are located outside the default paths:
 
 ```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/
+add-symbol-file "/arm-auto-solutions/build/tmp_baremetal/work/fvp_rd_aspen-poky-linux/linux-yocto-rt/6.12.30+git/linux-fvp_rd_aspen-preempt-rt-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.
@@ -73,7 +82,7 @@ You might see a warning like:
 ```text
 WARNING(ROS60): Could not enable OS support as the OS does not appear to be initialized. This might be caused by a mismatch between the loaded symbols and the code on the target or because the OS is not up and running. Enabling OS support will be re-attempted when the target next stops.
 ```
-This occurs if the OS has not completed boot when you connect; it is safe to ignore and will clear after the next target stop.
+This occurs if the OS has not completed boot when you connect; it is safe to ignore and will clear when stopping target after the OS has booted.
 {{% /notice %}}
 
 You have successfully learnt how to use Arm Development Studio to explore and debug the Arm Zena CSS Reference Software Stack.