infra: add miscellaneous changes for 2021.02.24 release

Add all the miscellaneous changes that have been identified for the
2021.02.24 release.

Change-Id: Idfbab46e4353b736bcdeb9b5646ef383bb206fdf
Signed-off-by: Thomas Abraham <thomas.abraham@arm.com>

docs/infra/common/busybox-boot.rst

@@ -203,6 +203,6 @@ Example commands to boot upto busybox are as listed below.
 
 --------------
 
-*Copyright (c) 2020, Arm Limited. All rights reserved.*
+*Copyright (c) 2020-2021, Arm Limited. All rights reserved.*
 
 .. _Download sources: docs/infra/common/download-sources.rst

docs/infra/common/distro-boot.rst

@@ -99,21 +99,21 @@ Examples of the build command are
     ./build-scripts/build-test-uefi.sh -p rdn2 clean
 
 - Command to perform an incremental build of the software components included in
-  the software stack for the RD-Daniel Config-XLR platform:
+  the software stack for the RD-V1 quad-chip platform:
 
   *Note:* this command should be followed by the ``package`` command to
   complete the preparation of the fip image.
 
   ::
 
-    ./build-scripts/build-test-uefi.sh -p rddanielxlr build
+    ./build-scripts/build-test-uefi.sh -p rdv1mc build
 
 - Command to package the previously built software stack and prepares the fip
   image:
 
   ::
 
-    ./build-scripts/build-test-uefi.sh -p rddanielxlr package
+    ./build-scripts/build-test-uefi.sh -p rdv1mc package
 
 
 Installing a linux distribution
@@ -172,7 +172,7 @@ Supported command line options are listed below
      to be enabled, use 'true' as the option. Default value is set to
      'false'.
 
-*  -a <additional_params>
+*  -a <additional_params> (optional)
 
    - Specify any additional model parameters to be passed. The model
      parameters and the data to be passed to those parameters can be found
@@ -183,10 +183,10 @@ An example of a command to install the debian distribution is listed below.
 
 ::
 
-  ./distro.sh -p rddaniel -i /absolute/path/to/debian-10.6.0-arm64-xfce-CD-1.iso -s 16
+  ./distro.sh -p rdv1 -i /absolute/path/to/debian-10.6.0-arm64-xfce-CD-1.iso -s 16
 
 
-- This command creates a 16GB SATA disk image, boots the RD-Daniel Config-M
+- This command creates a 16GB SATA disk image, boots the RD-V1 single-chip
   software stack and starts the installation of debian distribution.
 
 - From here on, follow the instructions of the choosen distribution
@@ -259,7 +259,7 @@ Supported command line options are listed below
       to be enabled, use 'true' as the option. Default value is set to
       'false'.
 
-*  -a <additional_params>
+*  -a <additional_params> (optional)
 
    -  Specify any additional model parameters to be passed. The model
       parameters and the data to be passed to those parameters can be found
@@ -273,18 +273,18 @@ Example commands to boot a linux distribution are listed below.
 
   ::
 
-    ./distro.sh -p rddaniel
+    ./distro.sh -p rdv1
 
 
 - Command to begin the distro boot from the ``fedora.satadisk`` image:
 
   ::
 
-    ./distro.sh -p rddaniel -d /absolute/path/to/fedora.satadisk
+    ./distro.sh -p rdv1 -d /absolute/path/to/fedora.satadisk
 
 
 --------------
 
-*Copyright (c) 2020, Arm Limited. All rights reserved.*
+*Copyright (c) 2020-2021, Arm Limited. All rights reserved.*
 
 .. _Download sources: docs/infra/common/download-sources.rst

docs/infra/common/download-sources.rst

@@ -68,19 +68,19 @@ the subsequent instructions.
 +--------------------------+-------------------------+
 | Reference Platform       | Manifest File Name      |
 +==========================+=========================+
-| SGI-575                  | pinned-sgi575.xml       |
+| RD-N2                    | pinned-rdn2.xml         |
 +--------------------------+-------------------------+
-| RD-N1-Edge (Single Chip) | pinned-rdn1edge.xml     |
+| RD-V1 (Single Chip)      | pinned-rdv1.xml         |
 +--------------------------+-------------------------+
-| RD-N1-Edge (Dual Chip)   | pinned-rdn1edge-dev.xml |
+| RD-V1 (Quad Chip)        | pinned-rdv1mc.xml       |
 +--------------------------+-------------------------+
-| RD-E1-Edge               | pinned-rde1edge.xml     |
+| RD-N1-Edge (Single Chip) | pinned-rdn1edge.xml     |
 +--------------------------+-------------------------+
-| RD-Daniel Config-M       | pinned-rddaniel-dev.xml |
+| RD-N1-Edge (Dual Chip)   | pinned-rdn1edgex2.xml   |
 +--------------------------+-------------------------+
-| RD-Daniel Config-XLR     | pinned-rddaniel-dev.xml |
+| RD-E1-Edge               | pinned-rde1edge.xml     |
 +--------------------------+-------------------------+
-| RD-N2                    | pinned-rdn2.xml         |
+| SGI-575                  | pinned-sgi575.xml       |
 +--------------------------+-------------------------+
 
 
@@ -159,4 +159,4 @@ of the GCC toolchain binaries and installation of the other prerequisites.
 
 --------------
 
-*Copyright (c) 2020, Arm Limited. All rights reserved.*
+*Copyright (c) 2020-2021, Arm Limited. All rights reserved.*

docs/infra/common/secure-boot.rst

@@ -257,28 +257,28 @@ There are additional steps to be performed on the first boot to setup the secure
 boot process. These steps are listed below. Ensure that these steps are executed
 on the very first boot for validating the secure boot.
 
-- Interrupt the boot at EDK2 by pressing escape key and dropping into the EDK2
-  boot menu.
-- Select Device Manger -> Secure Boot Configuration -> Secure Boot Mode →
-  choose Custom mode and then press enter.
-- Select "Custom Secure Boot Options” and then press enter.
-- Select “DBX Options” -> "Enroll Signature" then press enter →
-  "Enroll Signature Using File" and the press enter → Select “NO VOLUME LEBEL”
-  and then press enter.
-- Select EFI and press enter -> select BOOT and press enter → now Select
-  “DBX.der” and press enter -> “Commit Changes and Exit”.
-- Repeat steps “d” and “e” for “DB options” for “DB.der”.
-- Repeat steps “d” and “e” for “KEK options” for “KEK.der”.
-- Repeat steps “d” and “e” for “PK options” for “PK.der”.
-- Press Escape and press F10 to save. Ensure that the “Current Secure Boot
-  State” is set as “Enabled”.
-- Press Escape and select the “continue” option.
-- Prompts the user to press the “Enter”. Press Enter key which then reboots the
-  system
-- Make sure to close the model using “Cross Mark” on the FVP UI window titled
-  'Fast Models - <platform_name>' after this. If model does not close then press
-  “ctrl-c” to close it. Here, <platform_name> is one of those listed in
-  `Platform Names`_.
+1. Interrupt the boot at EDK2 by pressing escape key and dropping into the EDK2
+   boot menu.
+2. Select Device Manger -> Secure Boot Configuration -> Secure Boot Mode →
+   choose Custom mode and then press enter.
+3. Select "Custom Secure Boot Options” and then press enter.
+4. Select “DBX Options” -> "Enroll Signature" then press enter →
+   "Enroll Signature Using File" and the press enter → Select “NO VOLUME LEBEL”
+   and then press enter.
+5. Select EFI and press enter -> select BOOT and press enter → now Select
+   “DBX.der” and press enter -> “Commit Changes and Exit”.
+6. Repeat steps “4” and “5” for “DB options” for “DB.der”.
+7. Repeat steps “4” and “5” for “KEK options” for “KEK.der”.
+8. Repeat steps “4” and “5” for “PK options” for “PK.der”.
+9. Press Escape and press F10 to save. Ensure that the “Current Secure Boot
+   State” is set as “Enabled”.
+10. Press Escape and select the “continue” option.
+11. Prompts the user to press the “Enter”. Press Enter key which then reboots the
+    system.
+12. Make sure to close the model using “Cross Mark” on the FVP UI window titled
+    'Fast Models - <platform_name>' after this. If model does not close then
+    press “ctrl-c” to close it. Here, <platform_name> is one of those listed in
+    `Platform Names`_.
 
 Relaunch the model again with repeat the steps listed above to perform a secure
 boot (but skip the steps to enroll the signatures). The platform boots up to

docs/infra/common/winpe-boot.rst

@@ -100,21 +100,21 @@ Examples of the build command are
     ./build-scripts/build-test-uefi.sh -p rdn2 clean
 
 - Command to perform an incremental build of the software components included in
-  the software stack for the RD-Daniel Config-M platform:
+  the software stack for the RD-N2 platform:
 
   *Note:* this command should be followed by the ``package`` command to
   complete the preparation of the fip image.
 
   ::
 
-    ./build-scripts/build-test-uefi.sh -p rddaniel build
+    ./build-scripts/build-test-uefi.sh -p rdn2 build
 
 - Command to package the previously built software stack and prepares the fip
   image:
 
   ::
 
-    ./build-scripts/build-test-uefi.sh -p rddaniel package
+    ./build-scripts/build-test-uefi.sh -p rdn2 package
 
 
 Obtain the WinPE disk image
@@ -180,17 +180,17 @@ Supported command line options are listed below
 
 Example commands to boot WinPE are as listed below.
 
-- Command to begin the WinPE boot on the RD-Daniel platform using a
+- Command to begin the WinPE boot on the RD-N2 platform using a
   ``WinPE_arm64.iso`` pre-built disk image. Follow the instructions on console
   to complete the WinPE boot.
 
   ::
 
-    ./distro.sh -p rddaniel -d /absolute/path/to/WinPE_arm64.iso
+    ./distro.sh -p rdn2 -d /absolute/path/to/WinPE_arm64.iso
 
 
 --------------
 
-*Copyright (c) 2020, Arm Limited. All rights reserved.*
+*Copyright (c) 2020-2021, Arm Limited. All rights reserved.*
 
 .. _Download sources: docs/infra/common/download-sources.rst

docs/infra/rdn2/user-guide.rst → docs/infra/rdn2/readme.rst

-RD-N2 platform user guide
-=========================
+RD-N2 platform software user guide
+==================================
 
 .. contents::
 
@@ -9,16 +9,12 @@ Introduction
 
 RD (Reference Design) is a collection of resources to provide a representative
 view of typical compute subsystems that can be designed and implemented using
-specific generations of Arm IP.
-
-RD-N2 in particular is based on the following ARM IP's:
+specific generations of Arm IP. RD-N2 in particular is based on the following
+hardware configuration.
 
 - 32xMP1 Neoverse N2 CPUs
-
 - CMN-700 interconnect
-
 - Multiple AXI expansion ports for I/O Coherent PCIe, Ethernet, offload
-
 - Arm Cortex-M7 for System Control Processor (SCP) and
   Manageability Control Processor (MCP)