You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SystemReady SR band: update to v3.1.1 release and align component tags
- Update release version from v3.1.0 to v3.1.1
- Update prebuilt image reference to v26.03_3.1.1
- Align ACS components to latest tags/commits:
- BSA ACS updated to v26.03_BSA_1.2.1
- SBSA ACS updated to v26.03_SBSA_8.0.1
- SBMR ACS updated to v26.03_SBMR_2.1.0
- BBR updated to specific commit
- BBSR updated to specific commit
- UEFI-SCT commit updated
- Update EDK2 to edk2-stable202511
- Populate systemready-sr-band-source.cfg with required ACS tags
- xbsa git clone refactored in get_source.sh
- FWTS source moved to https://github.com/fwts/fwts/archive/refs/tags due to issue with fwts.ubuntu.com URL
Signed-off-by: Sathisha S <sathisha.shivaramappa@arm.com>
Copy file name to clipboardExpand all lines: SystemReady-band/README.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,29 +28,29 @@ SystemReady band compliant platforms must implement a minimum set of hardware an
28
28
The SystemReady band compliance and testing requirements are specified in the [Arm SystemReady Requirements Specification (SRS)](https://developer.arm.com/documentation/den0109/latest)
29
29
30
30
## Latest Release details
31
-
- Release version: v3.1.0
31
+
- Release version: v3.1.1
32
32
- Quality: EAC
33
-
- The latest pre-built release of ACS is available for download here: [v25.10_3.1.0](prebuilt_images/v25.10_3.1.0)
33
+
- The latest pre-built release of ACS is available for download here: [v26.03_3.1.1](prebuilt_images/v26.03_3.1.1)
34
34
- The compliance suite is not a substitute for design verification.
35
35
- To review the ACS logs, Arm licensees can contact Arm directly through their partner managers.
36
36
-**Image Test Suite details**
37
37
38
38
| Test Suite | Test Suite Tag / Commit | Specification Version |
Follow the steps below to decompress the pre-built image:
8
+
9
+
```bash
10
+
unzip systemready_acs_live_image.img.xz.zip
11
+
xz -d systemready_acs_live_image.img.xz
12
+
```
13
+
14
+
After decompression, you will get the .img file, which can be used directly with your target environment.
15
+
16
+
---
17
+
18
+
## Prerequisites
19
+
20
+
### OS Installation and Boot Logs
21
+
22
+
Arm SystemReady band v3.1.1 requires that OS installation and boot logs are used to check for overall compliance:
23
+
24
+
- Installation and boot logs from RHEL and SLES LTS releases are required.
25
+
26
+
To get the logs run the [linux-distro-cmds.sh](https://gitlab.arm.com/systemready/systemready-band-template/-/blob/main/os-logs/linux-distro-cmds.sh?ref_type=heads) script and copy RHEL and SLES logs into acs image root folder. Within acs image root folder, create os-logs then copy those RHEL and SLES logs into that folder
27
+
28
+
The ACS image root folder structure is as follows:
29
+
30
+
```
31
+
├── EFI
32
+
├── acs_tests
33
+
├── acs_results
34
+
├── os-logs
35
+
├── Image
36
+
└── ramdisk-buildroot.img
37
+
```
38
+
39
+
### SBMR Execution Mode
40
+
41
+
SBMR in-band tests are run as part of SystemReady ACS automation. The out-of-band SBMR tests need to be executed from outside the DUT, using an external host machine, to exercise the server system's out-of-band capabilities.
42
+
43
+
Please refer to the [SBMR ACS README.md](https://github.com/ARM-software/sbmr-acs/blob/main/README.md) for steps to run the tests.
44
+
45
+
After a successful run, the suite generates a `logs` folder containing run metadata and results in an XML file. This folder must be renamed to `sbmr_out_of_band_logs` and copied to the `acs_results\sbmr\` path in the ACS image, so that the log parser scripts can collate the results and provide an overall SBMR compliance report for the DUT.
0 commit comments