bsp: Restore the ability to build firmware only

To allow us to continue to ship Corstone-1000 releases that only include
the firmware with the built in Linux image we need a way to build it
outside of the multiconfig builds.

Signed-off-by: Drew Reed <Drew.Reed@arm.com>

ci/corstone1000-firmware-only.yml

@@ -0,0 +1,25 @@
+---
+header:
+  version: 14
+
+local_conf_header:
+  rescuebuild: |
+    # Need to ensure the rescue linux options are selected
+    OVERRIDES .= ":firmware"
+
+    # Need to ensure we build with a small libc
+    TCLIBC="musl"
+
+  mass-storage: |
+    # Ensure the Mass Storage device is absent
+    FVP_CONFIG[board.msd_mmc.p_mmc_file] = "invalid.dat"
+
+  test-configuration: |
+    TEST_SUITES = "_qemutiny ping"
+    # Remove Dropbear SSH as it will not fit into the corstone1000 image.
+    IMAGE_FEATURES:remove = "ssh-server-dropbear"
+    CORE_IMAGE_EXTRA_INSTALL:remove = "ssh-pregen-hostkeys"
+
+target:
+  - corstone1000-flash-firmware-image
+  - perf

meta-arm-bsp/conf/machine/include/corstone1000.inc

@@ -54,6 +54,7 @@ WKS_FILE:firmware ?= "corstone1000-flash-firmware.wks.in"
 # making sure EXTRA_IMAGEDEPENDS will be used while creating the image
 WKS_FILE_DEPENDS:append = " ${EXTRA_IMAGEDEPENDS}"
 
-# If not build under the firmware multiconf we need to build the actual firmware
-EXTRA_IMAGEDEPENDS = "${@bb.utils.contains('DISTROOVERRIDES', 'firmware', \
-                        '', 'firmware-deploy-image', d)}"
+# If not building under the firmware multiconf we need to build the actual firmware
+FIRMWARE_DEPLOYEMENT ?= "firmware-deploy-image"
+FIRMWARE_DEPLOYEMENT:firmware ?= ""
+EXTRA_IMAGEDEPENDS += "${FIRMWARE_DEPLOYEMENT}"