- Jan 19, 2019
-
-
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:Thomas Abraham <thomas.abraham@arm.com>
-
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:Jagadeesh Ujja <jagadeesh.ujja@arm.com>
-
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:Sughosh Ganu <sughosh.ganu@arm.com>
-
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:Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com>
-
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:Chandni Cherukuri <chandni.cherukuri@arm.com>
-
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:
-
- Oct 30, 2018
-
-
Commit ed0fed88 ("build-scp: specify target path for mcp rom binary") adds a unconditional access to MCP binary files. This is incorrect as MCP binary is built only for SGI platforms. Fix this by adding a check for presence of MCP build output folder. Change-Id: Icf60f0f4c10fbc60cb74bfd533d7dba9c086385f Reported-by:Asha R <asha.r@arm.com> Signed-off-by:
-
Change-Id: I2d86cfa2f31f22393d77dcd34adebfdea48b68f0 Signed-off-by:Nariman Poushin <nariman.poushin@linaro.org>
-
- Oct 19, 2018
-
-
The build command for upstream scp now requires a CC command line parameter that points to the absolute path of the compiler to be used for building scp. So adapt the scp build script to these changes in build command. Change-Id: I48442342739f57f6dcceb5e1d627e04421038d70 Signed-off-by:
-
- Oct 11, 2018
-
-
For disto boots, the entire stack need not be built. The components required to be built are scp, arm-tf and uefi. Add a new build script to build these components for distro boot test. This script is a wrapper on the build-all script. Change-Id: I19a44eb37acc1d8923a47c11d78a20122f922e81 Signed-off-by: -
Add a new build script to allow building the SGI stack for busybox boot. This script is a wrapper on the build-all script. After completing the build of the required components, this script prepares a boot disk image with EFI and ext3 paritions in it. Change-Id: I1302e72284fc8539b1a306e49c52f18815b0bd4d Signed-off-by: -
The grub config files will be selected by the test case that is being built. So there is no need to have default grub config files listed the platform specific build configuration file. Change-Id: I6a3dd2c41f4b4f95eddb1019e0a77194305e5804 Signed-off-by: -
The BL config stage is not required for SGI platforms. Add a new flag to conditionally enable the BL config stage. The platforms that need the BL config stage will have to enable it. Change-Id: I188a22de4118bcec19b98103d4909a207c2052ee Signed-off-by: -
u-boot build is not required for SGI platforms. So, u-boot build can be marked as disabled by default and platforms that need the u-boot stage should enable it. Change-Id: I45f8da49612e7578c27b3174cc4f791e17453b33 Signed-off-by: -
For some of the test cases such as distro-boot, it is not mandatory to build any of the supported filesystems. For such test cases, a new 'none' filesystem is introduced. The configuration file for the 'none' filesystem is an empty file. This approach is the least intrusive approach to avoid building filesystems for test cases that do not need any specific filesystem to be built. Change-Id: I8368a01cfdab33ec1bbe8da3568a5916a51d7627 Signed-off-by: -
Remove all the code related to preparation of the disk image for busybox and OE file systems from build-grub.sh file. This file should contain code that is only related build/package stage of grub. Change-Id: Id9fcccd560c03d6f9d67b8887f370398b450a1ff Signed-off-by: -
Allow wrappers of build-all.sh to optionally override build configs before the build stage. Change-Id: Ifae45d22599a66aa1664d60310cf75bab8cb1ca7 Signed-off-by: -
SGI platforms will have their own platform config file and there will be no need for a common sgi config file. So remove the common.sgi file and create a SGI-575 platform specific config file. Change-Id: Id8febae412a04ca16e040a2f07845e3eb3a76b93 Signed-off-by: -
SCPv2 build is supported by the scripts and SCPv2 generates a MCP rom binary as well. Allow the MCP rom binary to be copied to a specific target destination. Change-Id: Ia5539aca408e51cc986291a19507b84a76553eed Signed-off-by: -
Add SCPv2 build options for all SGI platforms. All the SGI platforms will have support for SCPv2. Hence, these options are applicable for all SGI platforms. Change-Id: I6a601c5ff41280baa70ea2a18ca5b2735c2e3557 Signed-off-by:
-
- Aug 10, 2018
-
-
Change-Id: I11e4272f0a635059b6536a8ba4e91036e12fc1d9 Signed-off-by: -
Asha R authored
Change-Id: I03bf6fdda427126ade3e4ea9f5975257fd2c7cf1 Signed-off-by:
-
- Aug 07, 2018
-
-
Arvind Chauhan authored
Change-Id: I2d9e49de82129cb50075395d13a055e08157e57b Signed-off-by: -
Arvind Chauhan authored
ARM_TF_DEBUG_ENABLED needs to be set to debug or release mode. Release mode build for TF-A is default setting. Change-Id: I2b0094e39c5ceb42994f9f3d8fec674fde8f72a1 Signed-off-by:
-
