OrgZephyr/mcuboot
OrgZephyr
/
mcuboot
mirror of https://github.com/zephyrproject-rtos/mcuboot.git
1
0
Fork 0
Code Issues Releases Wiki Activity
mcuboot/boot/zephyr/sample.yaml

60 lines
2.2 KiB
YAML
Raw Normal View History

zephyr: add zephyr's sanitycheck description Added sample.yaml which is required for automatic building mcuboot using zephyr sanitycheck. Can be run by zephyr sanitycheck locally using --testcase-root=/path/to/mcuboot/boot/zephyr to make it detect the sample.yaml added. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2019-12-12 18:04:43 +08:00
sample:
description: mcuboot test build sample
name: mcuboot
tests:
sample.bootloader.mcuboot:
tags: bootloader_mcuboot
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dk/nrf52840 frdm_k64f disco_l475_iot1
boot: zephyr: add integration platforms to the allow list The platforms that are listed as integration platforms in the Zephyr boot sample need to be included in the platform allow list, otherwise zephyr CI will throw an error. This commit removes the common list of integration platforms and adds integration platform entries in each test variant, in accordance with the allow-list in each of the variants. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-07-28 05:17:05 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dk/nrf52840
zephyr: ci: enable testing more watchdog paths Enable tests to be run on frdm_k64f and disco_l475_iot1. The l475 uses the STM32 IWDG by default, and the k64f can be used for the generic watchdog path. Both boards also received a config to enable the watchdog. Signed-off-by: Fabio Utzig <utzig@apache.org>
2022-09-11 07:18:30 +08:00
- frdm_k64f
- disco_l475_iot1
zephyr: add zephyr's sanitycheck description Added sample.yaml which is required for automatic building mcuboot using zephyr sanitycheck. Can be run by zephyr sanitycheck locally using --testcase-root=/path/to/mcuboot/boot/zephyr to make it detect the sample.yaml added. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2019-12-12 18:04:43 +08:00
sample.bootloader.mcuboot.serial_recovery:
extra_args: OVERLAY_CONFIG=serial_recovery.conf
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dk/nrf52840
boot: zephyr: add integration platforms to the allow list The platforms that are listed as integration platforms in the Zephyr boot sample need to be included in the platform allow list, otherwise zephyr CI will throw an error. This commit removes the common list of integration platforms and adds integration platform entries in each test variant, in accordance with the allow-list in each of the variants. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-07-28 05:17:05 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dk/nrf52840
zephyr: add zephyr's sanitycheck description Added sample.yaml which is required for automatic building mcuboot using zephyr sanitycheck. Can be run by zephyr sanitycheck locally using --testcase-root=/path/to/mcuboot/boot/zephyr to make it detect the sample.yaml added. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2019-12-12 18:04:43 +08:00
tags: bootloader_mcuboot
sample.bootloader.mcuboot.usb_cdc_acm_recovery:
tags: bootloader_mcuboot
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dongle/nrf52840
zephyr: fix handling of devicetree overlays in mcuboot The current specific setting of devicetree overlay files using `set()` has a couple of built-in flaws. It keeps readding the overlay file on each subsequent CMake invocation. The build command (make/ninja), will automatically invoke CMake if there are any changes to files used as configure time dependencies. This can easily be seen by manually re-invoking CMake: ``` # First invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: bootloader/mcuboot/boot/zephyr/dts.overlay # Second invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay ``` Zephyr has built-in support for application specific overlay config which gets automatically applied when the overlay file is named: `app.overlay`. Therefore rename `dts.overlay` to `app.overlay`. Ref: https://docs.zephyrproject.org/3.2.0/build/dts/howtos.html \ #set-devicetree-overlays This change further allows users of mcuboot to place their mcuboot configuration out-of-tree of the sample by using the `APPLICATION_CONFIG_DIR` setting. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-11-21 17:35:02 +08:00
extra_args: DTC_OVERLAY_FILE="./usb_cdc_acm.overlay;app.overlay"
boot: zephyr: add integration platforms to the allow list The platforms that are listed as integration platforms in the Zephyr boot sample need to be included in the platform allow list, otherwise zephyr CI will throw an error. This commit removes the common list of integration platforms and adds integration platform entries in each test variant, in accordance with the allow-list in each of the variants. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-07-28 05:17:05 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dongle/nrf52840
zephyr: allow recovery over usb cdc-acm with logs enabled Modified serial_adapter so log are allowed when using USB CDC ACM serial port emulation. Added dedicated thread for log processing of the highest application priority. This allows to transmit all logs without adding k_sleep anywhere else int the code. Introduced boot log thread is simpler than the default log threat which decreases flash footprint by a few dozen bytes. Added configuration for nrf52840_pca10056 which shows how to enable looging along with USB - among other, thread log processing is required. build command (form zephyr-project root directory) west build -d build/mcuboot/nrf52840_pca10056 -b nrf52840_pca10056 ./bootloader/mcuboot/boot/zephyr/ -- -DDTC_OVERLAY_FILE=./boards/nrf52840_pca10056_big.overlay -DOVERLAY_CONFIG=./usb_cdc_acm_log_recovery.conf Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2020-02-17 20:25:32 +08:00
sample.bootloader.mcuboot.usb_cdc_acm_recovery_log:
extra_args: OVERLAY_CONFIG=./usb_cdc_acm_log_recovery.conf
zephyr: fix handling of devicetree overlays in mcuboot The current specific setting of devicetree overlay files using `set()` has a couple of built-in flaws. It keeps readding the overlay file on each subsequent CMake invocation. The build command (make/ninja), will automatically invoke CMake if there are any changes to files used as configure time dependencies. This can easily be seen by manually re-invoking CMake: ``` # First invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: bootloader/mcuboot/boot/zephyr/dts.overlay # Second invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay ``` Zephyr has built-in support for application specific overlay config which gets automatically applied when the overlay file is named: `app.overlay`. Therefore rename `dts.overlay` to `app.overlay`. Ref: https://docs.zephyrproject.org/3.2.0/build/dts/howtos.html \ #set-devicetree-overlays This change further allows users of mcuboot to place their mcuboot configuration out-of-tree of the sample by using the `APPLICATION_CONFIG_DIR` setting. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-11-21 17:35:02 +08:00
DTC_OVERLAY_FILE="./boards/nrf52840_big.overlay;app.overlay"
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dk/nrf52840
boot: zephyr: add integration platforms to the allow list The platforms that are listed as integration platforms in the Zephyr boot sample need to be included in the platform allow list, otherwise zephyr CI will throw an error. This commit removes the common list of integration platforms and adds integration platform entries in each test variant, in accordance with the allow-list in each of the variants. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-07-28 05:17:05 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dk/nrf52840
zephyr: allow recovery over usb cdc-acm with logs enabled Modified serial_adapter so log are allowed when using USB CDC ACM serial port emulation. Added dedicated thread for log processing of the highest application priority. This allows to transmit all logs without adding k_sleep anywhere else int the code. Introduced boot log thread is simpler than the default log threat which decreases flash footprint by a few dozen bytes. Added configuration for nrf52840_pca10056 which shows how to enable looging along with USB - among other, thread log processing is required. build command (form zephyr-project root directory) west build -d build/mcuboot/nrf52840_pca10056 -b nrf52840_pca10056 ./bootloader/mcuboot/boot/zephyr/ -- -DDTC_OVERLAY_FILE=./boards/nrf52840_pca10056_big.overlay -DOVERLAY_CONFIG=./usb_cdc_acm_log_recovery.conf Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2020-02-17 20:25:32 +08:00
tags: bootloader_mcuboot
boot/zephyr: Added single-slot Zephyr-RTOS test build Added configuration for build in Zephyr-RTOS CI MCUBoot in CONFIG_SINGLE_APPLICATION_SLOT=y mode. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2020-09-15 19:15:02 +08:00
sample.bootloader.mcuboot.single_slot:
extra_args: OVERLAY_CONFIG=./single_slot.conf
zephyr: fix handling of devicetree overlays in mcuboot The current specific setting of devicetree overlay files using `set()` has a couple of built-in flaws. It keeps readding the overlay file on each subsequent CMake invocation. The build command (make/ninja), will automatically invoke CMake if there are any changes to files used as configure time dependencies. This can easily be seen by manually re-invoking CMake: ``` # First invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: bootloader/mcuboot/boot/zephyr/dts.overlay # Second invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay ``` Zephyr has built-in support for application specific overlay config which gets automatically applied when the overlay file is named: `app.overlay`. Therefore rename `dts.overlay` to `app.overlay`. Ref: https://docs.zephyrproject.org/3.2.0/build/dts/howtos.html \ #set-devicetree-overlays This change further allows users of mcuboot to place their mcuboot configuration out-of-tree of the sample by using the `APPLICATION_CONFIG_DIR` setting. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-11-21 17:35:02 +08:00
DTC_OVERLAY_FILE="./boards/nrf52840_single_slot.overlay;app.overlay"
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dk/nrf52840
boot: zephyr: add integration platforms to the allow list The platforms that are listed as integration platforms in the Zephyr boot sample need to be included in the platform allow list, otherwise zephyr CI will throw an error. This commit removes the common list of integration platforms and adds integration platform entries in each test variant, in accordance with the allow-list in each of the variants. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-07-28 05:17:05 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dk/nrf52840
boot/zephyr: Added single-slot Zephyr-RTOS test build Added configuration for build in Zephyr-RTOS CI MCUBoot in CONFIG_SINGLE_APPLICATION_SLOT=y mode. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2020-09-15 19:15:02 +08:00
tags: bootloader_mcuboot
boot: zephyr: add nrf52840 QSPI NOR overlays Add configuration and DTS overlays to run MCUboot + smp_svr on the nrf52840dk using the secondary slot in the external QSPI NOR flash. Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>
2020-11-09 21:03:22 +08:00
sample.bootloader.mcuboot.qspi_nor_slot:
zephyr: fix handling of devicetree overlays in mcuboot The current specific setting of devicetree overlay files using `set()` has a couple of built-in flaws. It keeps readding the overlay file on each subsequent CMake invocation. The build command (make/ninja), will automatically invoke CMake if there are any changes to files used as configure time dependencies. This can easily be seen by manually re-invoking CMake: ``` # First invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: bootloader/mcuboot/boot/zephyr/dts.overlay # Second invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay ``` Zephyr has built-in support for application specific overlay config which gets automatically applied when the overlay file is named: `app.overlay`. Therefore rename `dts.overlay` to `app.overlay`. Ref: https://docs.zephyrproject.org/3.2.0/build/dts/howtos.html \ #set-devicetree-overlays This change further allows users of mcuboot to place their mcuboot configuration out-of-tree of the sample by using the `APPLICATION_CONFIG_DIR` setting. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-11-21 17:35:02 +08:00
extra_args: DTC_OVERLAY_FILE="./boards/nrf52840dk_qspi_nor_secondary.overlay;app.overlay"
boot: zephyr: add nrf52840 QSPI NOR overlays Add configuration and DTS overlays to run MCUboot + smp_svr on the nrf52840dk using the secondary slot in the external QSPI NOR flash. Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>
2020-11-09 21:03:22 +08:00
OVERLAY_CONFIG="./boards/nrf52840dk_qspi_nor.conf;./boards/nrf52840dk_qspi_secondary_boot.conf"
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dk/nrf52840
boot: zephyr: add integration platforms to the allow list The platforms that are listed as integration platforms in the Zephyr boot sample need to be included in the platform allow list, otherwise zephyr CI will throw an error. This commit removes the common list of integration platforms and adds integration platform entries in each test variant, in accordance with the allow-list in each of the variants. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-07-28 05:17:05 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dk/nrf52840
boot: zephyr: add nrf52840 QSPI NOR overlays Add configuration and DTS overlays to run MCUboot + smp_svr on the nrf52840dk using the secondary slot in the external QSPI NOR flash. Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>
2020-11-09 21:03:22 +08:00
tags: bootloader_mcuboot
zephyr: Added hooks for example Example (very basic) hook implementation. Added case description for test-build with these hooks and multi-image feature. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2021-07-12 17:10:41 +08:00
sample.bootloader.mcuboot.hooks_multi:
zephyr: fix handling of devicetree overlays in mcuboot The current specific setting of devicetree overlay files using `set()` has a couple of built-in flaws. It keeps readding the overlay file on each subsequent CMake invocation. The build command (make/ninja), will automatically invoke CMake if there are any changes to files used as configure time dependencies. This can easily be seen by manually re-invoking CMake: ``` # First invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: bootloader/mcuboot/boot/zephyr/dts.overlay # Second invocation $ cmake -DBOARD=nrf52840dk_nrf52840 -DDTC_OVERLAY_FILE=custom.dts .. Loading Zephyr default modules (Zephyr workspace). -- Application: /projects/github/ncs/bootloader/mcuboot/boot/zephyr ... -- Found devicetree overlay: custom.dts -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay -- Found devicetree overlay: mcuboot/boot/zephyr/dts.overlay ``` Zephyr has built-in support for application specific overlay config which gets automatically applied when the overlay file is named: `app.overlay`. Therefore rename `dts.overlay` to `app.overlay`. Ref: https://docs.zephyrproject.org/3.2.0/build/dts/howtos.html \ #set-devicetree-overlays This change further allows users of mcuboot to place their mcuboot configuration out-of-tree of the sample by using the `APPLICATION_CONFIG_DIR` setting. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-11-21 17:35:02 +08:00
extra_args: DTC_OVERLAY_FILE="./boards/nrf52840dk_ram_multi.overlay;app.overlay"
zephyr: Added hooks for example Example (very basic) hook implementation. Added case description for test-build with these hooks and multi-image feature. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2021-07-12 17:10:41 +08:00
OVERLAY_CONFIG=./boards/nrf52840dk_hooks_sample_overlay.conf
zephyr: direct inclusion of the hooks file This patch removes CONFIG_BOOT_IMAGE_ACCESS_HOOKS_FILE option which was used to point to hooks implementation file. It is better that the project customization is up to add required files instead. This gives more flexibility in provisioning these sources (there may be multiple files). This also simplifies Kconfig options. In order to keep possibility for build-test the Hooks feature hooks_sample.c will be included into the build if commandline will specify -DTEST_BOOT_IMAGE_ACCESS_HOOKS=Y option. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2022-07-07 20:55:22 +08:00
TEST_BOOT_IMAGE_ACCESS_HOOKS=Y
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
platform_allow: nrf52840dk/nrf52840
zephyr: Added hooks for example Example (very basic) hook implementation. Added case description for test-build with these hooks and multi-image feature. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2021-07-12 17:10:41 +08:00
integration_platforms:
zephyr: Update board names for hwmv2 Updates board names as per hwmv2 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-02-08 22:04:19 +08:00
- nrf52840dk/nrf52840
zephyr: Added hooks for example Example (very basic) hook implementation. Added case description for test-build with these hooks and multi-image feature. Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
2021-07-12 17:10:41 +08:00
tags: bootloader_mcuboot
zephyr: Wrapped the RAM loading mode in Zephyr configs. The RAM loading mode wasn't wrapped in Zephyr configs like the other boot modes. Added a config to enable RAM loading as well as two configs to set IMAGE_EXECUTABLE_RAM_START and IMAGE_EXECUTABLE_RAM_SIZE, respectively. These two values default to the values from the chosen node sram in the dts. Signed-off-by: Johan Öhman <johan.ohman@softube.com>
2022-04-01 15:10:28 +08:00
sample.bootloader.mcuboot.ram_load:
extra_args: OVERLAY_CONFIG=./ram_load.conf
tags: bootloader_mcuboot
platform_allow: mimxrt1020_evk
integration_platforms:
- mimxrt1020_evk