- Feb 25, 2019
-
-
SGI-Clark.Helios platform can be used to boot into a UEFI shell. So allow the usability of this script on SGI-Clark.Helios platform. Change-Id: I0315cac81577b97f9235362c8e9b1a2f976b106f Signed-off-by:Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com>
-
SGI-Clark.Ares platform can be used to boot into a UEFI shell. So allow the usability of this script on SGI-Clark.Ares platform. Change-Id: I47af98022d9efbb0ab7f06bb3fe5f17bdb3e9c33 Signed-off-by: -
Thomas Abraham authored
SGI-Clark.Helios platform can be validated using ACS test suite. So enable usability of this script on SGI-Clark.Helios platform. Change-Id: Ifd903019fbf9f6f9477d17728d1cfef7061f77b6
-
Thomas Abraham authored
SGI-Clark.Ares platform can be validated using ACS test suite. So enable usability of this script on SGI-Clark.Ares platform. Change-Id: Id8abad4420e86435c1cbf255571db31cb4a1a26f Signed-off-by:Thomas Abraham <thomas.abraham@arm.com>
-
SGI-Clark.Ares uses a TF-A firmware to boot the application cores. So TF-A tests can be used on this platform to validate the port of TF-A on this platform. So allow the usability of this script on SGI-Clark.Ares platform. Change-Id: I9fb77167d9a446f65db6bdabb970fac13d4f0e1f Signed-off-by:Chandni Cherukuri <chandni.cherukuri@arm.com>
-
Add a initial set of build configurations for SGI-Clark.Helios platform. This initial configuration allows for busybox boot and other test cases to be exuected. Change-Id: Ide72ac8f6709915cf3bce4585d5dbd748ab1e034 Signed-off-by:
-
- Feb 22, 2019
-
-
Add a initial set of build configurations for SGI-Clark.Ares platform. This initial configuration allows for busybox boot and other test cases to be exuected. Change-Id: Ic7a09dd964022b5dbad83257bff0a71e22d2d61d Signed-off-by:
-
- Feb 19, 2019
-
-
Thomas Abraham authored
Enable SPM and RAS build flags by default for TF-A build. StandaloneMM is assumed to be always used as secure partition on SGI platforms and so these flags are being enabled by default. Change-Id: I33e993ab3b3d85a9fc633464a908709ed4a80b69 Signed-off-by: -
Add config options for building the StandaloneMM binary along with the build of uefi binary. Change-Id: Ie491f95dcd9c00efa987ec2cbd933369ebf9d243 Signed-off-by:Sughosh Ganu <sughosh.ganu@arm.com>
-
Add support for adding the StandaloneMM binary as the BL32 image in the gip binary. Change-Id: Ia3ba78aaa9385fa04b302d623da1b63100915185 Signed-off-by: -
In preparation to add the build of uefi StandaloneMM binary, allow platforms to override the name of the built image. When building StandaloneMM along with uefi, there are two build targets, one for non-secure uefi and one for StandaloneMM. So instead of fixing the built image name to 'uefi.bin', allow platform config file to override the name of the built image. Change-Id: If6b84ae5801b570a52bf6afa78edec76f0a9f0fa Signed-off-by: -
The busybox boot test script has reorganized the disk image preparation code. Do the same for secure busybox boot as well. In addition to this, add the build override macros for UEFI (SECURE_STORAGE_ENABLE=TRUE and SECURE_BOOT_ENABLE=TRUE") and do minor cleanup as well. Change-Id: I5dd709d96d20bdf8cf06d048fb8d0467ba15ae2b Signed-off-by:Jagadeesh Ujja <jagadeesh.ujja@arm.com>
-
- Feb 18, 2019
-
-
Thomas Abraham authored
There are changes to the location of the ACS build script in ACS v19.01_REL2.1 release. Adapt the build-acs script to adapt to these changes. Change-Id: I7efbc0fc2d2229625a3a0b52105d5e9b6c5687ef Signed-off-by: -
Thomas Abraham authored
Add the kernel module build support into the linux kernel component build script. The kernel module build can be enabled in the platform's config file by adding a build config as LINUX_foo[modules]="true" where 'foo' is the linux build configuration name. For instance, if 'defconfig' is the linux build configuration name, the platform config file can enable module build for defconfig using LINUX_defconfig[modules]="true" If kernel module compilation is not required for the build, either mark the config option as 'false' (LINUX_foo[modules]="false") or do not add this entry in the platform configuration file. If kernel module compilation is enabled, the package stage copies the compiled kernel modules to "output/<platform>/components/linux/modules/" Change-Id: I3a114d61dc61805efab9ed43536cb6d07e98609d Signed-off-by: -
The old ramdisk-oe.img format is causing issues on 5.0 kernels in which initramfs errors are no longer ignored: ff1522bb7d98 ("initramfs: cleanup incomplete rootfs") Update cpio command to use newc format, the new (SVR4) portable format, which does not cause issues on recent kernels. Signed-off-by:Ionela Voinescu <ionela.voinescu@arm.com>
-
Enable optee for FVP platforms in build scripts. Signed-off-by:Asha R <asha.r@arm.com>
-
- Jan 19, 2019
-
-
Define TFTF flags for SGI575 platform which are required for building the TFTF source code. Change-Id: Ied1b90ce3502f0ff4d09cbf5cbe5d17a3ce990df Signed-off-by: -
Add a config option SCT_OUT_DIR which specifies the SCT output directory to be used in SCT build and package stages. Change-Id: I003186e30cc98ab4e8ff9120479daf3c00c49067 Signed-off-by:
Lokesh B V <lokesh.bv@arm.com> -
Thomas Abraham authored
The existing build-sgiboot.sh script which is used to prepare the binary images for boot upto busybox shell is actually SGI specific. So move it into 'sgi' platform folder and rename it as build-test-busybox.sh. Change-Id: Iffa92f0d3565fbe5fccb28073b04d6cff95d9350 Signed-off-by: -
Add support for building the fip and disk images for validating secure boot functionality on Arm's SGI platforms. The build packages busybox as the filesystem and places all the required signatures into the EFI parition. Change-Id: Ie9f82f3954cc86dc44756256908cc98a2d2d4b11 Signed-off-by: -
Add support for building the sgi platform software stack for validating the RAS error injection and error handling capabilities. Except for grub, all the other components gets built as part of the build process. The build requires a prebuilt fedora disk image. The compiled linux kernel is loaded into this prebuilt disk image during the package stage. Change-Id: I93c99ef06b315a2cbfdb42d5fc7b5c0e269379a4 Signed-off-by: -
Add a new build script to allow building the SGI stack for UEFI SCT test. This script is a wrapper on the build-all script. After completing the build of the required components, this script prepares a disk image with EFI parition and UEFI SCT pre-installed in it. Change-Id: Iaa88ffa5f063d2a301babd1f376572c5aa82f85c Signed-off-by:Lokesh B V <lokesh.bv@arm.com> -
Add support for building the fip and disk images for validating kvm functionality on Arm's SGI platforms. Except for grub, all the other components gets built as part of the build process. The build requires a prebuilt fedora disk image. The compiled linux kernel image is loaded into this prebuilt disk image during the package stage. The kvmtool required to launch the virtual machines is expected to present in the fedora disk image. Change-Id: Ia0d446e549922680529f708ad13932b034a053b7 Signed-off-by: -
To build and execute the SGI platform software, certain host OS packages are expected to be pre-installed. This script helps with installing the required host packages. Change-Id: Ib7a9639b7722426c57b68e1b19a25d406c342047 Signed-off-by:Lokesh Belathur Veerappa <lokesh.belathurveerappa@arm.com>
-
Add support for preparing fedora disk for ras test by adding the sgi linux kernel entry in the fedora grub menu. Add support for kvm test by downloading and packaging lkvm executable in root directory of fedora disk. This script needs sudo permission for mouting the disk image and expects a installed fedora disk image in prebuilts/sgi folder. Change-Id: I3cb1ea72b9e77b7b1a78c8568a6d66d7f40e2883 Signed-off-by: -
Add a script file for building all the components required for a ACS test on a platform. Change-Id: Idc64233e67353ef8b1c24b6eb10a861b5a75ac3e Signed-off-by: -
Add a script file for building all the components required for a TFTF test on a platform. Change-Id: Ibedd3a6b71b08c438c462979797663d84625c190 Signed-off-by: -
Thomas Abraham authored
The existing distro boot test script does nothing more than building all the software components that are required to test booting to a uefi shell. So rename the distro boot script as a uefi boot test script. Change-Id: I2959d96a5633e7aef393719deef5f63d22e18d7e Signed-off-by: -
Thomas Abraham authored
Arm ACS is a test suite used to ensure that a server platform adheres to Arm's SBSA and SBBR specifications. Add a component build script to build Arm ACS test suite. Change-Id: I01f45e1596592d7f1e182aeea3536ca702ec11ed Signed-off-by: -
Add a component build script to support builidng of UEFI SCT package in edk2. Change-Id: If47384ab55fb29c7f35c0a6a3d4be6286a9ce74f Signed-off-by:Lokesh B V <lokesh.bv@arm.com> -
Allow build scripts to add additional build configurations. This allows build scripts to add build parameters during the build process. These build parameters should not be included in the platform build config file but instead created and exported during the build process. Change-Id: I3404c3c44de0f12015e943eeb708fc7e68b4a478 Signed-off-by: -
In case of a tftf test case build, neither u-boot nor uefi gets built and tftf.bin should be used as the BL33 image in FIP. So allow for tftf.bin to be packaged in fip for tftf test case build. Change-Id: I1f9b1a44349305c89ce2d308574b6647be707d7c Signed-off-by: -
By default, TFTF is not built so set TFTF_BUILD_ENABLED as 0 in common.base. Set to 1 only when TFTF build is required. Change-Id: I71ad0f013852b6d93b5cdd5591c076e889ea72d4 Signed-off-by: -
LINUX_COMPILER is used by build-tftf.sh script as the cross compiler toolchain. Define it in the common.base file so it is accessible for all platforms Change-Id: I21cb38abfc876d24267dce0bd3b0d352db2853fb Signed-off-by: -
Allow overriding of the default build configuration before calling the clean/build/package stages of the component build scripts. This is acheived by calling the __do_override_build_configs function which can be optionally implemented by the test case build script. Change-Id: I4f833df7582751aa50a1a945fc51a41d05f033b5 Signed-off-by:
-
- Jan 17, 2019
-
-
The existing method of overriding default build configurations by calling into __do_override_build_configs is useable only within the build-all.sh script. For component build scripts, __do_override_build_configs is not accessible and so component build script cannot override the default build configuration. So export the declaration of the override function if it is available so that component build scripts can override the default build configurations. Change-Id: I62621a2f59117541f71fe11b77a1b005fc030f62 Signed-off-by: -
Thomas Abraham authored
As build-scripts scales up to support platforms specfic tests, there is a need to create a platform specific directory to hold the platform specfic test build scripts. One of the ways to organize the platform specfic test build scripts could be as below build-scripts | |-- build-<component1>.sh |-- build-<component2>.sh |-- . |-- . |-- build-<componentX>.sh |-- build-test-TEST1.sh |-- build-test-TEST2.sh |-- . |-- . |-- build-test-TESTX.sh | |-- configs | | | |-- <platform1> | |-- <platform2> | |-- . | |-- . | |-- <platformX> | |-- <platform1> | | | |-- <build-test-TEST1>.sh | |-- <build-test-TEST2>.sh | |-- . | |-- . | |-- <build-test-TESTX>.sh | |-- <platform2> | | | |-- <build-test-TEST1>.sh | |-- <build-test-TEST2>.sh | |-- . | |-- . | |-- <build-test-TESTX>.sh | |-- <platformX> | |-- <build-test-TEST1>.sh |-- <build-test-TEST2>.sh |-- . |-- . |-- <build-test-TESTX>.sh The existing 'platforms' directory is in fact a bunch of build config files. So the 'platforms' directory can be renamed as 'configs' directory to allow adding platform specific directory under the root of build-scripts directory. This would help to avoid any possible incorrect interpretation of the purpose of the configs directory and the platform specific test build scripts directory. Change-Id: I3ca0576cfdbc7be88d2812fcda841c19c95ce8ca Signed-off-by:
-
- Jan 16, 2019
-
-
32 bit version of libfdt cause build issues for BL1. Delete libraries built during BL32 stage. Change-Id: I0893af63b4cbd92792f3189bf717d1b2122151ed Signed-off-by:Arvind Chauhan <arvind.chauhan@arm.com>
-
- Dec 25, 2018
-
-
Thomas Abraham authored
The ext3 partition in the busybox image gets a fixed UUID assigned to it during build. Use this UUID to identify the boot ext3 partition. Change-Id: I60866aa1afcd72708b57f59131e2a76749837d12 Signed-off-by: -
Thomas Abraham authored
The disk preparation code is reorganized to make it more readable. In addition to this, the functions are now parameterized and the ext3 partition gets a UUID assigned to it for use by grub. Change-Id: Icc8d380a7410de293c44aedcd705ed6a123da42d Signed-off-by:
-
