Skip to content

Commit 7090268

Browse files
authored
Merge pull request #2168 from odincodeshen/main
Update the infra RDN2 reference software stack instruction
2 parents 0acaf38 + 66e1dd7 commit 7090268

File tree

3 files changed

+54
-36
lines changed

3 files changed

+54
-36
lines changed

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/build-2.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,11 @@ Perform a build inside the container:
2121
```
2222

2323
During the build you will see that TF-A, UEFI and SCP firmware are built using their own build systems. The build finishes with the following output:
24+
2425
```output
25-
output/bin/grub-mkimage: info: kernel_img=0x7f366cf65010, kernel_size=0x1a000.
26-
output/bin/grub-mkimage: info: the core size is 0xa2a98.
27-
output/bin/grub-mkimage: info: writing 0xa5000 bytes.
26+
output/bin/grub-mkimage: info: kernel_img=0xf0a19d2c2010, kernel_size=0x1a000.
27+
output/bin/grub-mkimage: info: the core size is 0xa3040.
28+
output/bin/grub-mkimage: info: writing 0xa6000 bytes.
2829
Execute build for build-grub.sh on rdn2[rdn2][busybox] done.
2930
-----------------------------------
3031
***********************************

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/environment-setup-1.md

Lines changed: 48 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -39,28 +39,30 @@ repo version
3939
The output looks like this:
4040

4141
```output
42+
/usr/bin/repo:681: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
43+
now = datetime.datetime.utcnow()
4244
<repo not installed>
43-
repo launcher version 2.17
45+
repo launcher version 2.36
4446
(from /usr/bin/repo)
45-
git 2.34.1
46-
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
47-
OS Linux 6.2.0-1009-aws (#9~22.04.3-Ubuntu SMP Tue Aug 1 21:11:51 UTC 2023)
48-
CPU x86_64 (x86_64)
49-
Bug reports: https://bugs.chromium.org/p/gerrit/issues/entry?template=Repo+tool+issue
47+
git 2.43.0
48+
Python 3.12.3 (main, Jun 18 2025, 17:59:45) [GCC 13.3.0]
49+
OS Linux 6.8.0-1031-aws (#33-Ubuntu SMP Fri Jun 20 17:58:11 UTC 2025)
50+
CPU aarch64 (aarch64)
51+
Bug reports: https://issues.gerritcodereview.com/issues/new?component=1370071
5052
```
5153

5254
### Fetch source code
5355

5456
Create a new directory in to which you can download the source code, build the stack, and then obtain the manifest file.
5557

56-
To obtain the manifest, choose a tag of the platform reference firmware. [RD-INFRA-2023.09.29](https://neoverse-reference-design.docs.arm.com/en/latest/releases/RD-INFRA-2023.09.29/release_note.html) is used here, although it is recommended to use the latest version available. See the [release notes](https://neoverse-reference-design.docs.arm.com/en/latest/) for more information.
58+
To obtain the manifest, choose a tag of the platform reference firmware. [RD-INFRA-2025.07.03](https://neoverse-reference-design.docs.arm.com/en/latest/releases/RD-INFRA-2025.07.03/release_note.html) is used here, although it is recommended to use the latest version available. See the [release notes](https://neoverse-reference-design.docs.arm.com/en/latest/) for more information.
5759

5860
Specify the platform you would like with the manifest. In the [manifest repo](https://git.gitlab.arm.com/infra-solutions/reference-design/infra-refdesign-manifests) there are a number of available platforms. In this case, select `pinned-rdn2.xml`.
5961

6062
```bash
6163
mkdir rd-infra
6264
cd rd-infra/
63-
repo init -u https://git.gitlab.arm.com/infra-solutions/reference-design/infra-refdesign-manifests.git -m pinned-rdn2.xml -b refs/tags/RD-INFRA-2023.12.22
65+
repo init -u https://git.gitlab.arm.com/infra-solutions/reference-design/infra-refdesign-manifests.git -m pinned-rdn2.xml -b refs/tags/RD-INFRA-2025.07.03
6466
```
6567

6668
Now look at what the configured manifest contains:
@@ -104,24 +106,24 @@ The contents of `pinned-rdn2.xml` are shown below:
104106
<remote fetch="https://git.kernel.org" name="kernel"/>
105107
<remote fetch="https://git.trustedfirmware.org" name="tforg"/>
106108
107-
<project remote="arm" name="platsw/scp-firmware" path="scp" revision="refs/tags/RD-INFRA-2023.12.22"/>
108-
<project remote="arm" name="platsw/trusted-firmware-a" path="tf-a" revision="refs/tags/RD-INFRA-2023.12.22"/>
109-
<project remote="arm" name="platsw/edk2" path="uefi/edk2" revision="refs/tags/RD-INFRA-2023.12.22"/>
110-
<project remote="arm" name="platsw/edk2-platforms" path="uefi/edk2/edk2-platforms" revision="refs/tags/RD-INFRA-2023.12.22"/>
111-
<project remote="arm" name="platsw/linux" path="linux" revision="refs/tags/RD-INFRA-2023.12.22"/>
112-
<project remote="arm" name="scripts/build-scripts" path="build-scripts" revision="refs/tags/RD-INFRA-2023.12.22"/>
113-
<project remote="arm" name="scripts/model-scripts" path="model-scripts" revision="refs/tags/RD-INFRA-2023.12.22"/>
114-
<project remote="arm" name="scripts/container-scripts" path="container-scripts" revision="refs/tags/RD-INFRA-2023.12.22"/>
115-
<project remote="arm" name="valsw/kvm-unit-tests" path="validation/sys-test/kvm-unit-tests" revision="refs/tags/RD-INFRA-2023.12.22"/>
116-
<project remote="arm" name="platsw/buildroot" path="buildroot" revision="refs/tags/RD-INFRA-2023.12.22"/>
109+
<project remote="arm" name="platsw/scp-firmware" path="scp" revision="refs/tags/RD-INFRA-2024.12.20"/>
110+
<project remote="arm" name="platsw/trusted-firmware-a" path="tf-a" revision="refs/tags/RD-INFRA-2024.12.20"/>
111+
<project remote="arm" name="platsw/edk2" path="uefi/edk2" revision="refs/tags/RD-INFRA-2024.12.20"/>
112+
<project remote="arm" name="platsw/edk2-platforms" path="uefi/edk2/edk2-platforms" revision="refs/tags/RD-INFRA-2024.12.20"/>
113+
<project remote="arm" name="platsw/linux" path="linux" revision="refs/tags/RD-INFRA-2024.12.20"/>
114+
<project remote="arm" name="scripts/build-scripts" path="build-scripts" revision="refs/tags/RD-INFRA-2024.12.20"/>
115+
<project remote="arm" name="scripts/model-scripts" path="model-scripts" revision="refs/tags/RD-INFRA-2024.12.20"/>
116+
<project remote="arm" name="scripts/container-scripts" path="container-scripts" revision="refs/tags/RD-INFRA-2024.12.20"/>
117+
<project remote="arm" name="valsw/kvm-unit-tests" path="validation/sys-test/kvm-unit-tests" revision="refs/tags/RD-INFRA-2024.12.20"/>
118+
<project remote="arm" name="platsw/buildroot" path="buildroot" revision="refs/tags/RD-INFRA-2024.12.20"/>
117119
118120
<project remote="tforg" name="TF-A/tf-a-tests.git" path="validation/comp-test/trusted-firmware-tf" revision="6f9e14a0e3a9e14051cf6235a49b06bae32823d9"/>
119-
<project remote="github" name="acpica/acpica" path="tools/acpica" revision="refs/tags/R06_28_23"/>
120-
<project remote="github" name="ARMmbed/mbedtls.git" path="mbedtls" revision="refs/tags/mbedtls-2.28.0"/>
121-
<project remote="github" name="mirror/busybox" path="busybox" revision="refs/tags/1_36_0"/>
121+
<project remote="github" name="acpica/acpica" path="tools/acpica" revision="refs/tags/G20240322"/>
122+
<project remote="github" name="ARMmbed/mbedtls.git" path="mbedtls" revision="refs/tags/mbedtls-3.6.2"/>
123+
<project remote="github" name="mirror/busybox" path="busybox" revision="refs/tags/1_36_1"/>
122124
<project remote="gnugit" name="git/grub.git" path="grub" revision="refs/tags/grub-2.04"/>
123125
<project remote="kernel" name="pub/scm/linux/kernel/git/jejb/efitools" path="tools/efitools" revision="refs/tags/v1.9.2"/>
124-
<project remote="kernel" name="pub/scm/linux/kernel/git/will/kvmtool" path="kvmtool" revision="e17d182ad3f797f01947fc234d95c96c050c534b"/>
126+
<project remote="kernel" name="pub/scm/linux/kernel/git/will/kvmtool" path="kvmtool" revision="da4cfc3e540341b84c4bbad705b5a15865bc1f80"/>
125127
</manifest>
126128
```
127129

@@ -133,18 +135,26 @@ repo sync -c -j $(nproc) --fetch-submodules --force-sync --no-clone-bundle
133135
```
134136
The output from running this command looks like:
135137
```output
136-
... A new version of repo (2.40) is available.
137-
... New version is available at: /home/ubuntu/rd-infra/.repo/repo/repo
138+
139+
... A new version of repo (2.54) is available.
140+
... New version is available at: /home/ubuntu/rdn2-infra/.repo/repo/repo
138141
... The launcher is run from: /usr/bin/repo
139142
!!! The launcher is not writable. Please talk to your sysadmin or distro
140143
!!! to get an update installed.
141144
142-
Fetching: 100% (17/17), done in 2m23.399s
143-
Fetching: 100% (16/16), done in 26.300s
144-
Fetching: 100% (8/8), done in 11.914s
145-
Fetching: 100% (1/1), done in 0.592s
146-
Updating files: 100% (79368/79368), done.testsUpdating files: 26% (21084/79368)
147-
Checking out: 100% (42/42), done in 13.164s
145+
Fetching: 100% (17/17), done in 8m16.653s
146+
Fetching: 100% (17/17), done in 17.218s
147+
Fetching: 100% (17/17), done in 14.719s
148+
Fetching: 100% (7/7), done in 12.526s
149+
Fetching: 100% (1/1), done in 0.385s
150+
Updating files: 100% (84978/84978), done.ting files: 17% (14646/84978)
151+
Checking out: 27% (16/59), done in 8.804s
152+
Checking out: 28% (17/59), done in 0.779s
153+
Updating files: 100% (18459/18459), done.ptoPkg/Library/OpensslLib/openssl/pyca-cryptographyUpdating files: 42% (10441/24326)
154+
Updating files: 100% (24326/24326), done.ptoPkg/Library/OpensslLib/openssl/fuzz/corporaUpdating files: 54% (13137/24326)
155+
Checking out: 30% (18/59), done in 1.675s
156+
Checking out: 11% (7/59), done in 0.874s
157+
Checking out: 1% (1/59), done in 0.004s
148158
repo sync has finished successfully.
149159
```
150160
Now you should have all the code.
@@ -186,13 +196,19 @@ docker image list
186196
The output from this command looks like:
187197
```output
188198
REPOSITORY TAG IMAGE ID CREATED SIZE
189-
rdinfra-builder latest 8729adb0b96c 8 minutes ago 3.07GB
199+
rdinfra-builder latest e11c8e27a4c6 7 days ago 8.12GB
190200
ubuntu jammy-20230624 5a81c4b8502e 6 months ago 77.8MB
191201
```
192202

193203
The appearance of the output is like a standard ubuntu container based on the latest release with the rdinfra-builder container built on top. Let's run and enter the container:
194204
```bash
195-
docker run -it rdinfra-builder:latest /bin/bash
205+
docker run --rm \
206+
-v /home/ubuntu/rd-infra/:/home/ubuntu/rd-infra/ \
207+
-w /home/ubuntu/rd-infra/ \
208+
-e ARCADE_USER=$(id -un) \
209+
-e ARCADE_UID=$(id -u) \
210+
-e ARCADE_GID=$(id -g) \
211+
-it rdinfra-builder bash
196212
```
197213

198214
This command puts you in the running container where you can run `ls` to list the contents:

content/learning-paths/servers-and-cloud-computing/refinfra-quick-start/test-with-fvp-3.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ The firmware build can be executed on the Neoverse N2 Reference Design FVP that
1515

1616
Download the FVP from the previous page, or directly with:
1717
```bash
18-
wget https://developer.arm.com/-/media/Arm%20Developer%20Community/Downloads/OSS/FVP/Neoverse-N2/Neoverse-N2-11-24-12/FVP_RD_N2_11.24_12_Linux64.tgz
18+
wget https://developer.arm.com/-/cdn-downloads/permalink/FVPs-Neoverse-Infrastructure/RD-N2/FVP_RD_N2_11.25_23_Linux64.tgz
19+
1920
```
2021

2122
Unpack the tarball and run the install script:

0 commit comments

Comments
 (0)