- May 03, 2021
-
-
Add the initial build configuration file for RD-N2 Cfg1 platform. Support for busybox, uefi and secure boot has also been added. Signed-off-by:Aditya Angadi <aditya.angadi@arm.com> Change-Id: I8116b01146c97def39bca35ac54553f0b1260152
-
SCP_PLATFORM_VARIANT is a product specific build parameter passed using the build option PRODUCT_BUILD_PARAMS. It is used to configure a particular variant of a product. The default variant of RD-N2 platform has id 0. Provide the same as SCP_PLATFORM_VARIANT. Signed-off-by: -
An experimental patch in SCP has been introduced to allow SCP build system to accept product specific build options. This SCP patch is not upstream yet and it is uncertain if it will get upstreamed. For now, update the SCP firmware build script to allow the usage of the changes introduced by this SCP experimental patch. That is, allow SCP build script to supply additional product specific build options. Signed-off-by: -
The do_build() function of build-scp.sh copies the platform binaries from ${SCP_PATH} build folder into a common output folder. If build scp is executed for one platform (say PLAT1), and package scp is executed for another platform (say PLAT2), instead of copying PLAT2's SCP binaries, the package stage of build-scp.sh would copy PLAT1's binaries, since there's no separate platform folder in the output folder of ${SCP_PATH}. To fix this, create platform folder within the output folder of ${SCP_PATH} and copy from output/${plat}/* instead of output/*. This would ensure that if the package is called for PLAT2, it would copy PLAT2's binaries instead of binaries of previously build platform. Change-Id: I6a68e1cec9972b6dd395b9e109f7a041c15ca43b Signed-off-by:Vijayenthiran Subramaniam <vijayenthiran.subramaniam@arm.com>
-
For kvm build there are no separate requirements as the buildroot filesystem is used that already supports kvmtool and other packages required for kvm testing. So drop kvm build script. For any kvm testing, build buildroot to get required boot images. Signed-off-by:Vivek Gautam <vivek.gautam@arm.com> Change-Id: Iecbf47f24c76ad75b3a9009b0dde9d3c04037bed
-
Copy test binaries for smmu test engine to enable testing smmu test engine on various platforms. Signed-off-by: -
User-space driver for smmu test engine lies in tools directory. Build these iommu tools to get user-space smmute driver and test binary. Signed-off-by: -
Add a new build flag 'EDK2_ENABLE_EINJ' to selectively enable or disable error injection support for a platform. Signed-off-by:Omkar Anand Kulkarni <omkar.kulkarni@arm.com> Change-Id: I4ed02b5c82fa62e15b7a71262489b136c03de26f
-
Thomas Abraham authored
Introduce a flag 'ARM_TF_RAS_FW_FIRST' that can then be used to enable the required poritions of the firmware stack to support firmware first error handling. Signed-off-by:Thomas Abraham <thomas.abraham@arm.com> Change-Id: Iaf6a2e2f742b1e78ed8c8b1383d836d72f1f566b
-
Thomas Abraham authored
The definition MM_SECURE_STORAGE_ENABLE isn't used for the secure storage support in edk2-platforms. So remove this definition. Signed-off-by:
-
- Feb 19, 2021
-
-
Enable uefi secureboot build for multiple neoverse reference design platforms - rdn1edgex2, rdv1, rdv1mc, rdn2. Signed-off-by:Sayanta Pattanayak <sayanta.pattanayak@arm.com> Change-Id: I61ad02b3c73e4166d57ede85ce07ca4406fd56fd
-
StandaloneMM image name for RD-N1-Edge dual-chip platform is incorrect. Fix this by specifying the correct name for the image. Signed-off-by: -
Enable the use of secure partitions based on SPM implementation of trusted firmware. The secure partition support is required to enable the use of secure boot on the RD-N2 platform. Signed-off-by: -
Enable the use of secure partitions based on SPM implementation of trusted firmware. The secure partition support is required to enable the use of secure boot on the RD-V1 quad-chip platform. Signed-off-by: -
Enable the use of secure partitions based on SPM implementation of trusted firmware. The secure partition support is required to enable the use of secure boot on the RD-V1 platform. Signed-off-by: -
Enable the use of secure partitions based on SPM implementation of trusted firmware. The secure partition support is required to enable the use of secure boot on the RD-N1-Edge dual-chip platform. Signed-off-by: -
Flag ARM_TF_RAS_EXTENSION shall not be enabled by default. Enable this flag only for platforms that support RAS. Signed-off-by: -
The flag EL3_EXCEPTION_HANDLING must be enabled to compile trusted firmware with secure partion support. So allow this flag to the enabled even if RAS_EXTENSION is not enabled for the platform. Signed-off-by: -
The build flag 'EDK2_ENABLE_RAS' is does not provide the flexibility to choose the components a platforms needs to provide firmware-first error handling. So introduce additional build macros and use those macros on platforms that require it. Signed-off-by: -
Thomas Abraham authored
ARM_TF_BUILD_FLAGS should start with an empty string and should be appended to itself before adding additional macros to it. Fix this up for all the infra reference platforms. In addition to this, remove the unused ENABLE_SPM flag. Signed-off-by: -
Thomas Abraham authored
Setting ARM_TF_ENABLE_SPM=1 causes the the build flag CSS_SGI_CHIP_COUNT to be discarded. Fix this by reordering the position at which the flag CSS_SGI_CHIP_COUNT is assigned its value. Signed-off-by:
-
- Feb 11, 2021
-
-
Merge the two grub configs for busybox into one config and enable dhcp by default. Signed-off-by: -
build-busybox is already added to BUILD_SCRIPTS for each platform. Let's not add its definition again for busybox filesystem. Signed-off-by: -
Add a script to build buildroot based filesystem that can be booted on Neoverse reference design platforms. Signed-off-by: -
Add necessary build script to support building and packaging buildroot filesystem. Buildroot is richer in comparison to busybox and is also easier to add user-specific binaries, libraries, packages or other custom dev scripts etc. Signed-off-by: -
Buildroot works on defconfig against which the packages are built. For each platform, add a defconfig that can be copied to buildroot directory to allow the buildroot sources to be built. Signed-off-by: -
Add linux, grub and filesystem related config file to support the build of buildroot on neoverse refernce design platforms. Signed-off-by: -
Thomas Abraham authored
Instead of using helper scripts in uefi-tools to build the edk2 targets, add support for building edk2 targets into build-uefi script. This allows moving away from depending on the use of uefi-tools repo. In addition to this, update the build configs for each platform to specify the platform description files that have to be built. While at it, fix a typo in the array name used in the config file of rdn1edgex2 platform. Signed-off-by:
-
- Jan 07, 2021
-
-
Thomas Abraham authored
Instead of depending on a separate directory outside of build-scripts to hold the supporting files required to create the cpio image, migrate those supporting files into build-scripts. This helps with removing the dependency on requiring a separate repo to host these supporting files. Signed-off-by:
-
- Dec 18, 2020
-
-
Reference Design platform RD-Daniel-ConfigXLR has been renamed to RD-V1-MC. Correspondingly, remove all uses of 'rddanielxlr' and replace it with rdv1mc where appropriate. Signed-off-by: -
Reference Design platform RD-Daniel has been renamed to RD-V1. Correspondingly, remove all uses of 'rddaniel' and replace it with rdv1 where appropriate. Signed-off-by:
-
- Nov 28, 2020
-
-
Thomas Abraham authored
Update the grub menu entry name as "SGI-575 Busybox". This indicates the platform on which the grub loads the next stage of software. Signed-off-by:
-
- Nov 27, 2020
-
-
Thomas Abraham authored
All the platforms have virtio.net enabled on them. So the use of SMSC Lan91x controller can be removed. Signed-off-by: -
Add the initial build configuration files for RD-N2 platform. Support for uefi and busybox boot is also enabled. Change-Id: Iea2fa0ea0e0f2ccd6bcffd8775d6e0d59a1d76fb Signed-off-by:
-
- Oct 11, 2020
-
-
Vijayenthiran Subramaniam authored
Using build-target-bins on Ubuntu 20.04 results in the following error: "uboot_out: invalid indirect expansion" Ubuntu 20.04 LTS uses bash version 5.0 which doesn't expand an indirect expansion if the variable is not defined, which caused the above error. Fix this by checking if the uboot_out variable is not empty before doing the indirect expansion. Change-Id: Ie6e235f76809c40f36735b2e5844f668f89eff11 Signed-off-by: -
Vijayenthiran Subramaniam authored
Use $PARALLELISM for make builds to spawn multiple jobs. This results in better utilization of multi-core processor in the host machine used for build resulting in lesser build time. Change-Id: I2986a0ba3baf1db7409f55c018a4ebbcf6ccbc73 Signed-off-by: -
Vijayenthiran Subramaniam authored
'doxygen' package is required to build documentation for SCP-Firmware. So add it to the list of prerequisite packages to be installed. Change-Id: I7c152f7399f72023717f550b17bbf7fea5bc2c80 Signed-off-by:
-
- Oct 09, 2020
-
-
EDK2_ENABLE_RAS compilation flag was incorrectly being defined for builds with RAS disabled. Fix this for all the SGI/RD platfotms. Change-Id: I01209f6f03ca26c3b2e16c415856630cbf45c6e2 Signed-off-by: -
Update the name of the compiler binary for using the compiler from Arm developer site. This change corresponds to the compiler name as used in gcc-arm-8.3-2019.03-x86_64-arm-eabi version of the compiler. Change-Id: I93f162fb0ab318fbf049a46c26a8885102982d60 Signed-off-by: -
Instead of letting the common config file choose the compiler for the platform, let the platform config choose the most suitable compiler for the platform. Change-Id: I994a200ec5959704d0f361158a7a6f79c74d0a60 Signed-off-by:
-
