CSS-V3 Pre-Silicon update after ATG review

Author: odincodeshen

assets/contributors.csv

@@ -95,4 +95,5 @@ Chenying Kuo,Adlink,evshary,evshary,,
 William Liang,,,wyliang,,
 Waheed Brown,Arm,https://github.com/armwaheed,https://www.linkedin.com/in/waheedbrown/,,
 Aryan Bhusari,Arm,,https://www.linkedin.com/in/aryanbhusari,,
-Ken Zhang, Insyde,,,,
+Ken Zhang,Insyde,,,,
+Ann Cheng,Arm,anncheng-arm,hello-ann,,

content/learning-paths/servers-and-cloud-computing/neoverse-rdv3-swstack/1_introduction_rdv3.md

@@ -39,11 +39,13 @@ The CSS‑V3 subsystem is fully supported by Arm's Fixed Virtual Platform, enabl
 The RD‑V3 platform is a comprehensive reference design built around Arm’s [Neoverse V3](https://www.arm.com/products/silicon-ip-cpu/neoverse/neoverse-v3) CPUs, along with [Cortex-M55](https://www.arm.com/products/silicon-ip-cpu/cortex-m/cortex-m55) and [Cortex-M7](https://www.arm.com/products/silicon-ip-cpu/cortex-m/cortex-m7) microcontrollers. This platform enables efficient high-performance computing and robust platform management:
 
 
-| Component     | Description                                                                 |
-|---------------|-----------------------------------------------------------------------------|
-| Neoverse V3   | The primary application processor responsible for executing OS and payloads |
-| Cortex M7     | Implements the System Control Processor (SCP) for power, clocks, and init   |
-| Cortex M55    | Hosts the Runtime Security Engine (RSE), providing secure boot and runtime integrity |
+| Component        | Description                                                                                    |
+|------------------|------------------------------------------------------------------------------------------------|
+| Neoverse V3      | The primary application processor responsible for executing OS and payloads                    |
+| Cortex M7        | Implements the System Control Processor (SCP) for power, clocks, and init                      |
+| Cortex M55       | Hosts the Runtime Security Engine (RSE), providing secure boot and runtime integrity           |
+| Cortex M55 (LCP) | Acts as the Local Control Processor, enabling per-core power and reset management for AP cores |
+
 
 These subsystems work together in a coordinated architecture, communicating through shared memory regions, control buses, and platform protocols. This enables multi-stage boot processes and robust secure boot implementations.
 
@@ -76,6 +78,7 @@ To support different use cases and levels of platform complexity, Arm offers thr
 | RD‑V3       | Standard single-die platform with full processor and security blocks | Ideal for newcomers, firmware bring-up, and basic validation        |
 | RD‑V3‑R1    | Dual-die platform simulating chiplet-based architecture          | Suitable for multi-node, interconnect, and advanced boot tests     |
 | CFG1        | Lightweight model with reduced control complexity for fast startup | Best for CI pipelines, unit testing, and quick validations         |
+| CFG2        | Quad-chip platform with 4×32-core Poseidon-V CPUs connected via CCG links | Designed for advanced multi-chip validation, CML-based coherence, and high-performance platform scaling         |
 
 
 This Learning Path begins with RD‑V3 as the primary platform for foundational exercises, guiding you through the process of building the software stack and simulating it on FVP to verify the boot sequence.

content/learning-paths/servers-and-cloud-computing/neoverse-rdv3-swstack/3_rdv3_sw_build.md

@@ -52,7 +52,7 @@ cd rdv3
 repo init -u https://git.gitlab.arm.com/infra-solutions/reference-design/infra-refdesign-manifests.git -m pinned-rdv3.xml -b refs/tags/RD-INFRA-2025.07.03 --depth=1
 
 # Sync the full source code
-repo sync -c -j $(nproc) --fetch-submodules --force-sync --no-clone-bundle
+repo sync -c -j $(nproc) --fetch-submodules --force-sync --no-clone-bundle --retry-fetches=5
 ```
 
 Once synced, you will see the message like:
@@ -148,18 +148,15 @@ REPOSITORY        TAG       IMAGE ID       CREATED         SIZE
 rdinfra-builder   latest    3a395c5a0b60   4 minutes ago   8.12GB
 ```
 
-
-###  Step 4: Enter the Container and Build Firmware
-
-You can enter the Docker container interactively to quick look the image.
+To quickly test the Docker image you just built, run the following command to enter it interactively:
 
 ```bash
 cd ~/rdv3/container-scripts
 ./container.sh -v ~/rdv3 run
 ```
 
-This mounts your source directory (~/rdv3) into the container and opens a shell at that location.
-Inside the container, you’ll see a prompt like:
+This script mounts your source directory (~/rdv3) into the container and opens a shell session at that location.
+Inside the container, you should see a prompt like this:
 
 ```
 Running docker image: rdinfra-builder ...
@@ -169,13 +166,18 @@ See "man sudo_root" for details.
 your-username:hostname:/home/your-username/rdv3$
 ```
 
-Since building the full firmware stack can involve many components, the more efficient method is to use a single Docker command that runs both build and package steps automatically.
+You can explore the container environment if you wish, then type exit to return to the host system.
+
+
+###  Step 4: Enter the Container and Build Firmware
+
+Building the full firmware stack involves compiling several components and preparing them for simulation. Rather than running each step manually, you can use a single Docker command to automate the build and package phases.
 
 - **build**: This phase compiles all individual components of the firmware stack, including TF‑A, SCP, RSE, UEFI, Linux kernel, and rootfs.
 
 - **package**: This phase consolidates the build outputs into simulation-ready formats and organizes boot artifacts for FVP.
 
-To execute the full build and packaging flow:
+Ensure you’re back in the host OS, then run the following command:
 
 ```bash
 cd ~/rdv3

content/learning-paths/servers-and-cloud-computing/neoverse-rdv3-swstack/4_rdv3_on_fvp.md

@@ -37,8 +37,9 @@ The FVP installation may prompt you with a few questions—choosing the default
 
 The RD‑V3 FVP model launches multiple UART consoles—each mapped to a separate terminal window for different subsystems (e.g., Neoverse V3, Cortex‑M55, Cortex‑M7, panel).
 
-If you're accessing the platform over SSH, these console windows won't open properly.  
-To interact with all UART consoles, we recommend installing a Remote Desktop environment using XRDP.
+If you’re accessing the platform over SSH, these UART consoles can still be displayed, but network latency and graphical forwarding can severely degrade performance.
+
+To interact with different UARTs more efficiently, we recommend installing a remote desktop environment using `XRDP`. This provides a smoother user experience when dealing with multiple terminal windows and system interactions.
 
 In AWS Ubuntu 22.04 instance, you need install required packages:
 

content/learning-paths/servers-and-cloud-computing/neoverse-rdv3-swstack/_index.md

@@ -19,6 +19,7 @@ prerequisites:
 
 author:
     - Odin Shen
+    - Ann Cheng
 
 ### Tags
 skilllevels: Advanced

content/learning-paths/servers-and-cloud-computing/openbmc-rdv3/5_openbmc_xxx.md

@@ -0,0 +1,10 @@
+---
+title: Simulate Dual Chip RD-V3-R1 Platform
+weight: 6
+
+### FIXED, DO NOT MODIFY
+layout: learningpathall
+---
+
+## Redfish or IPMI APIs content?
+