- Mar 17, 2023
-
-
Tony Nadackal authored
Update arm-tf references to tf-a in script file names and its usage inside the script and config file. This is for maintaining consistency with Trusted Firmware-A (TF-A) and to avoid disambiguation from Trusted Firmware-M (TF-M) [1]. BREAKING CHANGE: With this change, the build-tf-a.sh script (previously build-arm-tf.sh) expects tf-a (instead of arm-tf) to be present in the workspace for successful build. [1]: https://github.com/ARM-software/arm-trusted-firmware/commit/4def07d5352893a33af18b04795f875fabff14de Signed-off-by:
Tony Nadackal <tony.nadackal@arm.com> Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: I5bb7c9658641589de4269aba21285a1c0474e9b2
-
Tony Nadackal authored
Update all variable references of Arm Trusted Firmware to Trusted Firmware-A (TF-A). This is for consistency with and disambiguation from Trusted Firmware-M (TF-M) [1]. [1]: https://github.com/ARM-software/arm-trusted-firmware/commit/4def07d5352893a33af18b04795f875fabff14de Signed-off-by:
Tony Nadackal <tony.nadackal@arm.com> Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: I8de6f7212c1e5bc701bf4ad311c0b6695e66f91f
-
- Mar 16, 2023
-
-
Install openssl in tools to avoid overriding the system ssl. If installed globally, the system ssl gets destroyed as it's unistalled and installed again by install_openssl3_0 function in sgi/install_prerequisites.sh, which changes the state of the ssl. This causes an issue in other application tasks which use ssl. Signed-off-by:
Sushant Tripathi <sushant.tripathi@arm.com> Change-Id: I474ccb085726593b80c60dbd699f2b77c25c310c
-
- Mar 14, 2023
-
-
gcc-6 and g++-6 are not used to build the reference platforms so can be safely removed from the list of required packages. Signed-off-by:
Sushant Tripathi <sushant.tripathi@arm.com> Change-Id: Ib3240100795bb7183ce3b2b2c053dd7ba80aa14c
-
- Feb 13, 2023
-
-
Every instance of repo directory needs a copy of toolchain taking up large disk space. Now we can have single toolchain directory for multiple repo instances. To use, define TC_PATH environment variable as the toolchain location. Signed-off-by:
Arnold Gabriel Benedict <ArnoldGabriel.Benedict@arm.com> Change-Id: I70838a7e53676766327c8e8f0ab285af69df1132
-
- Dec 22, 2022
-
-
Vivek Kumar Gautam authored
Enable LINUX_TOOLS_IOMMU_BUILD flag to build Linux iommu tools that builds smmute test binaries for IO virtualization tests. Signed-off-by:
Vivek Gautam <vivek.gautam@arm.com> Change-Id: If8d1be004ee1fccb40df77e7d1029852f6724a58
-
Vivek Kumar Gautam authored
The size of ext3 partition in the partition table was incorrectly set to $((ext3_part_size-1)). The size should match the size of the allocated parittion while creating the partition. So fix this mismatch in multiple build scripts, viz. build-test-busybox.sh, build-test-buildroot.sh, build-test-secureboot.sh. Signed-off-by:
Vivek Gautam <vivek.gautam@arm.com> Change-Id: Ie5b4b42dcb98b04e66c941bcbaaf03e2d5b5f10d
-
Since RD-N2-Cfg1 platform no longer supports ACS test, build script is modified to remove its support. Signed-off-by:
Tony Nadackal <tony.nadackal@arm.com> Change-Id: I6d368a10348dafcab6efedb25abe33ac6d61cdc9
-
This patch enables SPMC at EL3 configuration for rdn2cfg2 platform. Signed-off-by:
Nishant Sharma <nishant.sharma@arm.com> Change-Id: I5fda47ce6d3f7ffcf5cbc21d7f0df6a6cdd941c2
-
This patch enables SPMC at EL3 configuration for rdn2cfg2 platform. Signed-off-by:
Nishant Sharma <nishant.sharma@arm.com> Change-Id: Id4f2ed7a142276cfd5a07f804573d29fcf53b304
-
TOS_FW_CONFIG is used as configuration file for trusted services. In Arm infrastructure reference design platforms StMM is used as secure partition and the secure partition manager uses secure partition config file to prepare the execution context for secure partition. TOS_FW_CONFIG file has details about memory regions, device regions, runtime execution configuration etc. This file will be used by EL3 Secure Partition manager before handing over control to secure partition (StMM). This patch includes the tos_fw_config file into FIP for use by EL3 SPMC during TF-A execution. Signed-off-by:
Sayanta Pattanayak <sayanta.pattanayak@arm.com> Change-Id: Ia014461278644b520b57c825f31b9e188873609f
-
- Dec 21, 2022
-
-
This patch enables SPMC at EL3 configuration for rdn2 platform. Signed-off-by:
Nishant Sharma <nishant.sharma@arm.com> Change-Id: If6860a4084348bd6467c68a10bf84dc2e13ef693
-
This patch enables SPMC at EL3 configuration for rdn2cfg1 platform. Signed-off-by:
Nishant Sharma <nishant.sharma@arm.com> Change-Id: Ib343056daf0ba203ae68364d072144f1419733fd
-
Add CXL config fragment file for rdn2cfg1. Enable CXL specific kernel configurations. Add the config fragment file to defconfig's config list. Signed-off-by:
Sayanta Pattanayak <sayanta.pattanayak@arm.com> Change-Id: I689a44cf6618773b5d8066637e41039098fa9721
-
With NUMACTL configuration enabled in buildroot, NUMA test utilities (NUMASTAT, NUMADEMO) will be available for performing various NUMA specific test on all available NUMA nodes in kernel. Signed-off-by:
Sayanta Pattanayak <sayanta.pattanayak@arm.com> Change-Id: I78b303d732b49c12d4a9a2be01f4d0b71c1f1d07
-
Adds a build flag for enabling CXL remote memory configuration in UEFI. Signed-off-by:
Sayanta Pattanayak <sayanta.pattanayak@arm.com> Change-Id: Iff9fbd995f9d284d70f2665553c3dee9a2a9fc9a
-
As per advisory for CVE-2022-3602 and CVE-2022-3786 [1][2], upgrade openssl to 3.0.7. [1] https://www.openssl.org/news/secadv/20221101.txt [2] https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: I40cfb7dcfbc6640f9596de44cba7aa6afdc37c65
-
Tony Nadackal authored
Add the initial build configuration file for RD-N2-Cfg3 platform. Support for busybox, buildroot, uefi and secure boot is enabled. Signed-off-by:
Tony K Nadackal <tony.nadackal@arm.com> Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: Iae9d84131dc15b7604813e67e2e731a08577e02c
-
- Dec 05, 2022
-
-
Omkar Kulkarni authored
Rename the flag HANDLE_EA_EL3_FIRST to HANDLE_EA_EL3_FIRST_NS as updated in the TFA framework. Signed-off-by:
Omkar Anand Kulkarni <omkar.kulkarni@arm.com> Change-Id: I8a08c39cc5544b6d7c9866c5fea8d64b7af68ce0
-
- Sep 29, 2022
-
-
Define a flag and enable it to build kvmtool and kvm-unit-tests for rdv2 platform. Also define a variable describing the kvmtool supported platform to help decide output directory while packaging the binary. Add the kvmtool/kvm-unit-tests build script to the original BUILD_SCRIPTS list as well allowing it to be the part of whole stack building. Signed-off-by:
Sathyam Panda <sathyam.panda@arm.com> Change-Id: I55cf58c31fa038d0fefcbf1697f839296a29ae81
-
Define and add ArmVirtKvmTool package to the existing list of RD-V2 UEFI packages to build and provide firmware that can be used for UEFI based guest OS boot in a virtualized environment created with the help of kvmtool and linux KVM. Also define EDK2_OUT_DIR flag to point to the output directory to build ArmVirtKvmTool as current build-scripts don't create any ArmVirtKvmTool-$(ARCH) output directory. Signed-off-by:
Sathyam Panda <sathyam.panda@arm.com> Change-Id: Idd204fe402f98c81f399bcd0bc79752050a0a624
-
- Sep 28, 2022
-
-
GNU GRUB autogen.sh defaults to using the python command which defaults to python2 version. This is not available on newer Linux distributions since the EOL of python2 [1]. To resolve this, override the PYTHON environment variable to python3 when building grub. [1]: https://www.python.org/doc/sunset-python-2/ Note: this change will not be required when grub is updated with the latest version which includes following commit: https://git.savannah.gnu.org/cgit/grub.git/commit/?id=8f35208db4154ede690a18e408375815bbf320b7 Signed-off-by:
Joel Goddard <Joel.Goddard@arm.com> Change-Id: I8b9b36e5ba97e07b50ecb5bdba1ac3ce90be043b
-
add-apt-repository command fails in Ubuntu 18.04. To resolve this, install software-properties-common before invoking the add-apt-repository command. In addition to that, add -y to add-apt-repository command to prevent the script from waiting for user input. Signed-off-by:
Joel Goddard <joel.goddard@arm.com> Change-Id: I6572cb6ee3954f1d206212640c93002258e09cf4
-
This reverts commit 052e11c6. Linux kernel patches for SMMU Test Engine are now available and can be used with the related smmute tools scripts to test I/O virtualization use-case. So revert the change that disabled LINUX_TOOLS_IOMMU_BUILD build config. Change-Id: I506dee124c8bbd52c80fd33f4b6dec025d695c92 Signed-off-by:
Vivek Gautam <vivek.gautam@arm.com>
-
Vijayenthiran Subramaniam authored
Change the build configurations of RD-V2 based on the host machine architecture. Environment variable BUILD_MACHINE_ARCH is used for host specific changes in the configuration. Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: I5dcd58db499c9e99ee1b3f3c4a151435a19f025c
-
Add rdv2 platform support in the build-test-tftf.sh script. Signed-off-by:
Shriram K <shriram.k@arm.com> Change-Id: I47b93e9df841228ad0387ebbdfe1fd6c6767ffd2
-
Add tftf build flags in the rdv2 platform config file. Signed-off-by:
Shriram K <shriram.k@arm.com> Change-Id: I51855884d5069693fd15550240cfe83e4070c75a
-
- Sep 27, 2022
-
-
Shriram authored
Print a message that the tftf build has completed successfully, at the end of script execution. Signed-off-by:
Shriram K <shriram.k@arm.com> Change-Id: I2891f93df13c70b0bc481ce2d7e76ef32c7e84cd
-
Shriram authored
Add a workaround for the invalid indirect expansion error encountered when the software stack is built with $UEFI_BUILD_ENABLED set to zero(eg: tftf) on a Ubuntu 20.04 machine. The error occurs when the if condition checks the value assigned to local variable $uefi_out. Signed-off-by:
Shriram K <shriram.k@arm.com> Change-Id: Ie8ec7c3332597175011048c2ba7a03722869434a
-
Introduce platform build options: - CSS_SGI_FW_FIRST_SUPPORT: TFA build option to enable firmware first implementation on the RD-N2-Cfg1 platform. - CSS_SGI_ERR_INJ_SUPPORT: TFA build option to enable error injection support on RD-N2-Cfg1 platform. Default value is set to 1 as RD-N2-Cfg1 platform has either firmware-first or kernel-first error handling enabled. Signed-off-by:
Omkar Anand Kulkarni <omkar.kulkarni@arm.com> Change-Id: I39a1c3e4ef3d1120a22ffe8abcfa481a9858768c
-
Set this flag to enable kernel first error handing on RD-N2-Cfg1. This flag is disbaled by default. Signed-off-by:
Omkar Anand Kulkarni <omkar.kulkarni@arm.com> Change-Id: I2378740a6a13785746c95176e855db2c059b7ccd
-
Enable build options to add firmware first error handling support for Base Element RAM on RD-N2-Cfg1 platform. Signed-off-by:
Omkar Anand Kulkarni <omkar.kulkarni@arm.com> Change-Id: I941f127a95b390a7192f4ce749f5fc01691f7084
-
Introduce MPAM config fragment file for rdn2cfg1. Add kernel configurations required for enabling MPAM to the file. Additionally, add the config fragment file to defconfig's config list if MPAM is enabled for the platform. Signed-off-by:
Rohit Mathew <rohit.mathew@arm.com> Change-Id: I26158d822145a4d18b40e754773d7689bcab099c
-
Current build-system uses a base defconfig to build .config file for linux. Though there is a provision to pass additional config fragments, these are not properly appended to a base defconfig generated .config and are treated as separate config files altogther. The existing framework also uses an outdated config fragment path. Revise and re-introduce fragments framework. Instead of treating fragments as individual configs, treat them as additions or deletion of configs from the existing .config built from base defconfig. Make use of existing build framework to pass one or more config fragments. Fragments are appended to the .config file generated from defconfig one at a time. The kernel image is finally built with the appended .config. Signed-off-by:
Rohit Mathew <rohit.mathew@arm.com> Change-Id: Ib572a591ed6b27a0daf7e50d763e9a5411257df2
-
For software at lower exception levels than EL3 to access MPAM system registers without trapping, MPAM system register for EL3 should be configured accordingly. Define 'ENABLE_MPAM_FOR_LOWER_ELS' build option provided by Arm Trusted Firmware for RD-N2-Cfg1 and set it to '1' to enable MPAM access from lower ELs. Signed-off-by:
Rohit Mathew <rohit.mathew@arm.com> Change-Id: I6c347cb18b0eecc40d78f57b28a20693f2000f67
-
Booting with buildroot currently experience delays due to missing entropy for /dev/random etc. Enabling RNG_TOOLS also doesn't help with buildroot. So disable the PACKAGE_URANDOM_SCRIPTS for now to avoid running the random-number-generator start-up scripts that cause the boot delay. Signed-off-by:
Vivek Gautam <vivek.gautam@arm.com> Change-Id: If897eb5a579f52bf7ff51f779d49ba6ad98faa8b
-
Vijayenthiran Subramaniam authored
When building buildroot on a x86_64 host, BR2_TOOLCHAIN_EXTERNAL should be set to y to indicate that an external toolchain should be used to build for aarch64 target. Add a new x86_64 host specific config fragment for buildroot and move out the x86_64 host specific config into this file from the defconfig file. Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: I379414f48d37884834a214400e933aba5b1e5af5
-
Vijayenthiran Subramaniam authored
Buildroot can be build on both x86_64 and aarch64 host machines. The config files required to build on either of these host machines can be different. In order to support build of buildroot on both x86_64 and aarch64 host machines, add support to pick config fragments specific to the host machines and merge them with the base configuration. Once the merge is done, delete the config file which is copied to the buildroot's configs folder. With this support, $BUILDROOT_DEFCONFIG file will hold the configs that is common across both architectures. $BUILDROOT_X86_64_HOST_CONFIG file can hold configs that are specific to x86_64 host and $BUILDROOT_AARCH64_HOST_CONFIG file can hold configs that are specific to aarch64 host. Signed-off-by:
Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com> Change-Id: Id39a7ad3379348ae53b37309707b49f15b45987c
-
Vijayenthiran Subramaniam authored
Previously mkfs.ext3 was used to create an ext3 partition on a zero-filled raw image file and then mount that partition to a mount point using fuse-ext2 tool. The Linux and ramdisk images were then copied to this mount point. fusermount tool was used to sync the contents and unmount the partition. Also, tune2fs utility was needed to assign the UUID for this partition. fuse-ext2 tool is not available for AArch64 host machines by default. To avoid this dependency, a single mkfs.ext3 command is used to create an ext3 partition with UUID out of the raw image file. Signed-off-by:
Vijayenthiran Subramanaiam <vijayenthiran.subramaniam@arm.com> Change-Id: I623923c1de21f08dabe8fe8b82659eaccf7739e0
-
- Sep 26, 2022
-
-
Add rdn2cfg1 platform support in the build-test-tftf.sh script. Signed-off-by:
Shriram K <shriram.k@arm.com> Change-Id: I6b9c385464627860cf0345f89ac95c5daec307b6
-