Arm Enterprise ACS - Architecture Compliance Suite
Architecture Compliance Suite
Architecture Compliance Suite (ACS) is used to ensure architectural compliance across different implementations of the architecture. Arm Enterprise ACS includes a set of examples of the invariant behaviours that are provided by a set of specifications for enterprise systems (e.g. SBSA, SBBR, etc.), so that implementers can verify if these behaviours have been interpreted correctly. ACS is delivered with tests in source form along with a build script, the output of the build being a bootable Linux UEFI Validation (LUV) OS image that can run all tests required by these specifications.
Arm Enterprise ACS tests are available open source. The tests and the corresponding abstraction layers are available with an Apache v2 license allowing for external contribution.
In summary, the Arm Enterprise ACS product contains the following:
- Scripts to build, construct, and run the test images.
- A bootable LUV OS image capable of running all tests.
- Documentation on running the tests.
These tests are split between UEFI and Linux (supported by corresponding kernel driver) applications that together determine whether an architectural implementation is compliant with the enterprise specifications. These tests are further described in detail.
- Code Quality: REL v2.3
- The SBSA tests are written for version 5.0 of the SBSA specification.
- The SBBR tests are written for version 1.1 of the SBBR specification.
- The compliance suite is not a substitute for design verification.
- To review the ACS logs, Arm licensees can contact Arm directly through their partner managers.
- To pick up the release version of the code, checkout the release branch with the appropriate tag.
- To get the latest version of the code with bug fixes and new features, use the master branch.
ACS build steps
- Prebuilt images for each release are available in the prebuilt_images folder of the release branch. You can choose to use these images or build your own image by following the steps below.
- If you choose to use the prebuilt image, skip the build steps and jump to the test suite execution section below.
Before starting the ACS build, ensure that the following requirements are met:
- Ubuntu 16.04 LTS with at least 64GB of free disk space.
- Must use Bash shell.
Note : Windows build steps will be provided in the future releases.
Perform the following steps to start the ACS build:
- Create a directory that is your workspace and `cd' into it.
$ mkdir <work_dir> && cd <work_dir>
- Clone the Arm Enterprise ACS source code.
$ git clone https://github.com/ARM-software/arm-enterprise-acs.git
$ cd arm-enterprise-acs
- Download and patch LUV OS source code.
- Build LUV OS and test binaries.
- These build steps only target AArch64.
- The build script provides the option to append kernel command-line parameters, if necessary. Press enter to continue with default parameters.
- For build options to selectively sync and build particular modules, please check this document : build-options.
The luv-live-image-gpt.img bootable image can be found in:
This image comprises of two FAT file system partitions recognized by UEFI:
Stores logs and is used to install UEFI-SCT. (Approximate size: 120 MB)
Contains bootable applications and test suites. (Approximate size: 60 MB)
The PXE boot package containing the netbootable image grub-efi-bootaa64.efi can be found in:
This package may be used in PXE Booting and automatic execution of tests.
For more details please check this document : pxeboot-instructions.
Test Suite Execution
Juno Reference Platform
After installing the EDK2 prebuilt configuration on your Juno board, follow these steps:
- Burn the LUV OS bootable image to a USB stick:
$ sudo dd if=/path/to/luv-live-image-gpt.img of=/dev/sdX
Note: Replace '/dev/sdX' with the handle corresponding to your USB stick as identified by the `lsblk' command.
- Insert the USB stick into one of the Juno's rear USB ports.
- Power cycle the Juno.
Fixed Virtual Platform (FVP) environment
The steps for running the Arm Enterprise ACS on an FVP are the same as those for running on Juno but with a few exceptions:
Follow the different instructions here to install an EDK2 (UEFI) prebuilt configuration on your FVP.
Modify 'run_model.sh' to add a model command argument that loads 'luv-live-image-gpt.img' as a virtual disk image. For example, if running on the AEMv8-A Base Platform FVP, add
`bp.virtioblockdevice.image path=<work_dir>/arm-enterprise- acs/luv/build/tmp/deploy/images/qemuarm64/luv-live-image-gpt.img'
to your model options.
To launch the FVP model with script ‘run_model.sh’ that supports -v option for virtual disk image, use the following command:
$ ./run_model.sh -v <work_dir>/arm-enterprise-acs/luv/build/tmp/deploy/images/qemuarm64/luv-live-image-gpt.img
The test suite execution can be automated or manual. Automated execution is the default execution method when no key is pressed during boot.
Note: SBBR SCT tests are now included as part of automation. For information about running these tests, see section ‘SBBR SCT tests’ in this document.
The execution varies depending on the test environment. The next set of commands are an example of our typical run of the test suites. Note that the File System Partition in your platform can vary.
The live image boots to UEFI Shell. The different test applications can be run in following order:
- UEFI Shell application for SBSA compliance.
- SCT tests (if included in the build), for SBBR compliance.
- FWTS tests for SBBR compliance.
- OS tests for SBSA compliance.
Baselines for Open Source Software in this release:
Linux UEFI Validation OS - SHA: 73f995b61a7b1b856a082203cbeb744a3f21880d
UEFI Self Certification Tests (UEFI-SCT) TAG: b558bad25479ec83d43399673d7580294c81c8f8
Arm Enterprise ACS is distributed under Apache v2.0 License.
Feedback, contributions, and support
- For feedback, use the GitHub Issue Tracker that is associated with this repository.
- For support, please send an email to "firstname.lastname@example.org" with details.
- Arm licensees can contact Arm directly through their partner managers.
- Arm welcomes code contributions through GitHub pull requests. For details, see "docs/Contributions.txt".