NSIB nRF54H20 support - no partition manager #22274

ahasztag · 2025-05-13T11:30:19Z

The most of the changes introduced are related to getting rid of partition manager dependencies, however there are a couple of strictly nRF54H20 related changes.

The main changes introduced by this PR are:

Specifying the devicetree labels for the needed partitions:
In case of the NSIB + MCUBOOT configuration the labels are:
b0_partition - for placing the B0 code itself
provision_partition - for placing the "provisioning" information (app_provision.hex)
boot_partition - for placing the MCUBOOT S0 image
boot_partition_slot1 - for placing the MCUBOOT S1 image
slot0_partition - application primary slot
slot1_partition - mcuboot secondary slot

In case NSIB without MCUBOOT is used, slot0_partition and slot1_partition are used to specify the S0 and S1 images.

Ensuring devicetree consistency across all of the images. This is done in the cmake/sysbuild/bootloader_vars_preparation.cmake file. The code in this file checks that the all the needed partitions (with labels mentioned in (1)) point to the same nodes across all images. It also checks if zephyr,code-partition points to the appropriate partition for every image (for example boot_partition for the mcuboot image and so on)
PM_ symbols in CMake as well in the source code/header files are replaced by values taken from the device tree.
Changes needed due to the fact that instead of using an additional _pad partition before every image (which was the case with partition manager), the CONFIG_ROM_START_OFFSET is used to add MCUBOOT padding. This has several implications, such the need to calculate the NSIB signatures from a certain offset - asCONFIG_ROM_START_OFFSET causes the start of the image to be filled with zeroes, which are filled by imgtool after signing the image for NSIB.
Workarounds for OTP memory for nRF54H20 - the LCS/Key management/Monotonic counters on nRF54H20 will be handled in a different manner than for older devices, probably through SSF services. However, these services are not available yet. Thus, to mimic the NSIB functionality without the needed services being present, MRAM instead of OTP is used.

Note: the nrf54h20dk/nrf54h20/cpuapp/iron/mcuboot/b0 board was added in zephyr. This might not be the final approach. Other ways of specifying the memory map might be used.

NordicBuilder · 2025-05-13T11:31:46Z

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
mcuboot	nrfconnect/sdk-mcuboot@`766081b` (`main`)	nrfconnect/sdk-mcuboot#432	nrfconnect/sdk-mcuboot#432/files

⛔ DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

NordicBuilder · 2025-05-13T11:32:32Z

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 34

Inputs:

Sources:

sdk-nrf: PR head: f528302c977793cebf2edc084c01993078750ec5
mcuboot: PR head: f84e75fbb5eba5cc6adc98ddc03e53b3b1113cf4

more details

sdk-nrf:

PR head: f528302c977793cebf2edc084c01993078750ec5
merge base: 4b58475a68ea0590a33e1a7748abf5fdeb75afea
target head (main): ac6cabd1e0555bd0aeb4412e09eaec41330bac55
Diff

mcuboot:

PR head: f84e75fbb5eba5cc6adc98ddc03e53b3b1113cf4
merge base: 766081bd6dfe26057fdbe3dca5d8eb5f64681beb
target head (main): 766081bd6dfe26057fdbe3dca5d8eb5f64681beb
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (55)

CODEOWNERS
boards
│  ├── nordic
│  │  ├── nrf54h20dk
│  │  │  ├── Kconfig.defconfig
│  │  │  ├── Kconfig.nrf54h20dk
│  │  │  ├── Kconfig.sysbuild
│  │  │  ├── board.cmake
│  │  │  ├── board.yml
│  │  │  ├── nrf54h20dk_nrf54h20-memory_map_iron_b0_mcuboot.dtsi
│  │  │  ├── nrf54h20dk_nrf54h20_cpuapp_iron_b0_mcuboot.dts
│  │  │  ├── nrf54h20dk_nrf54h20_cpuapp_iron_b0_mcuboot_0_9_0.yaml
│  │  │  │ nrf54h20dk_nrf54h20_cpuapp_iron_b0_mcuboot_defconfig
bootloader
│  ├── mcuboot
│  │  ├── boot
│  │  │  ├── bootutil
│  │  │  │  ├── include
│  │  │  │  │  ├── bootutil
│  │  │  │  │  │  │ nrf_partitions.h
│  │  │  │  ├── src
│  │  │  │  │  ├── loader.c
│  │  │  │  │  ├── swap_move.c
│  │  │  │  │  ├── swap_nsib.c
│  │  │  │  │  ├── swap_priv.h
│  │  │  │  │  │ swap_scratch.c
│  │  │  ├── zephyr
│  │  │  │  ├── boards
│  │  │  │  │  │ nrf54h20dk_nrf54h20_cpuapp_iron_b0_mcuboot.conf
│  │  │  │  ├── include
│  │  │  │  │  ├── sysflash
│  │  │  │  │  │  ├── nsib_sysflash.h
│  │  │  │  │  │  │ sysflash.h
│  │  │  │  │ main.c
cmake
│  ├── sysbuild
│  │  ├── b0_mcuboot_signing.cmake
│  │  ├── bootloader_dts_utils.cmake
│  │  ├── image_signing.cmake
│  │  ├── provision_hex.cmake
│  │  ├── secureboot_merge.cmake
│  │  │ sign.cmake
include
│  ├── bl_partitions.h
│  ├── bl_storage.h
│  │ fw_info.h
samples
│  ├── bootloader
│  │  ├── CMakeLists.txt
│  │  ├── boards
│  │  │  ├── nrf54h20dk_nrf54h20_cpuapp_iron.conf
│  │  │  ├── nrf54h20dk_nrf54h20_cpuapp_iron.overlay
│  │  │  ├── nrf54h20dk_nrf54h20_cpuapp_iron_b0_mcuboot.conf
│  │  │  │ nrf54h20dk_nrf54h20_cpuapp_iron_b0_mcuboot.overlay
│  │  ├── include
│  │  │  │ bl_partitions_dummy.h
│  │  ├── src
│  │  │  │ main.c
│  │  ├── sysbuild
│  │  │  │ s1_image.overlay
│  ├── zephyr
│  │  ├── subsys
│  │  │  ├── mgmt
│  │  │  │  ├── mcumgr
│  │  │  │  │  ├── smp_svr
│  │  │  │  │  │  ├── CMakeLists.txt
│  │  │  │  │  │  ├── README.txt
│  │  │  │  │  │  ├── prj.conf
│  │  │  │  │  │  │ sample.yaml
scripts
│  ├── bootloader
│  │  ├── do_sign.py
│  │  ├── hash.py
│  │  ├── tests
│  │  │  │ validation_data_test.py
│  │  │ validation_data.py
subsys
│  ├── bootloader
│  │  ├── Kconfig
│  │  ├── bl_boot
│  │  │  │ bl_boot.c
│  │  ├── bl_storage
│  │  │  │ bl_storage.c
│  │  ├── bl_validation
│  │  │  │ bl_validation.c
│  ├── fw_info
│  │  ├── Kconfig
│  │  ├── fw_info.c
│  │  │ fw_info.ld
sysbuild
│  ├── CMakeLists.txt
│  │ secureboot.cmake
west.yml

Outputs:

Toolchain

Version: 4aa3467a6d
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:4aa3467a6d_e85602c25f

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

◻️ Toolchain - Skipped: existing toolchain is used
❌ Build twister
❌ Integration tests
- ❌ test-sdk-audio
- ❌ desktop52_verification
- ❌ test-fw-nrfconnect-boot
- ❌ test-fw-nrfconnect-apps
- ❌ test_ble_nrf_config
- ❌ test-fw-nrfconnect-ble_mesh
- ❌ test-fw-nrfconnect-ble_samples
- ❌ test-fw-nrfconnect-chip
- ❌ test-fw-nrfconnect-nfc
- ❌ test-fw-nrfconnect-nrf-iot_cloud
- ❌ test-fw-nrfconnect-nrf-iot_libmodem-nrf
- ❌ test-fw-nrfconnect-nrf-iot_serial_lte_modem
- ❌ test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
- ❌ test-fw-nrfconnect-nrf-iot_samples
- ❌ test-fw-nrfconnect-nrf-iot_lwm2m
- ❌ doc-internal
- ❌ test-fw-nrfconnect-nrf-iot_thingy91
- ❌ test-fw-nrfconnect-nrf_crypto
- ❌ test-fw-nrfconnect-proprietary_esb
- ❌ test-fw-nrfconnect-rpc
- ❌ test-fw-nrfconnect-rs
- ❌ test-fw-nrfconnect-fem
- ❌ test-fw-nrfconnect-tfm
- ❌ test-fw-nrfconnect-thread-main
- ❌ test-sdk-find-my
- ❌ test-fw-nrfconnect-nrf-iot_mosh
- ❌ test-fw-nrfconnect-nrf-iot_positioning
- ❌ test-sdk-wifi
- ❌ test-low-level
- ❌ test-sdk-pmic-samples
- ❌ test-sdk-mcuboot
- ❌ test-fw-nrfconnect-ps-main
- ❌ test-secdom-samples-public
- ⚠️ test-fw-nrfconnect-fw-update
- ⚠️ test-sdk-dfu

Note: This message is automatically posted and updated by the CI

github-actions · 2025-05-13T12:19:30Z

You can find the documentation preview for this PR here.

nordicjm · 2025-05-13T14:20:07Z

Kconfig.nrf

this should go in the board file, not here

nordicjm · 2025-05-13T14:22:57Z

cmake/sysbuild/b0_mcuboot_signing.cmake

will accept, though need to get the upstream hex merging system reviewed and use that eventually

Do you mean this one: zephyrproject-rtos/zephyr#83085 ?

I am still unsure how would we handle the B0 case. Specifically

the build/app_provision.hex file is not related to any image... There does not seem to be a mechanism to add this file to merged.hex

I am also signed_by_mcuboot_and_b0_mcuboot.hex and signed_by_mcuboot_and_b0_s1_image.hex - although these are connected to images they are generated by sysbuild, not by the the image cmake. But most of all, it seems that merging only supports files pointed to by one of the three variables: CONFIG_KERNEL_BIN_NAME, BYPRODUCT_KERNEL_SIGNED_HEX_NAME and BYPRODUCT_KERNEL_SIGNED_CONFIRMED_HEX_NAME - so there seemingly is not way using files generated for NSIB, there might be a need of a noup change here.

that provision file needs to go, it is awful, so it will not be a problem - see NCSDK-31918

nordicjm · 2025-05-13T14:26:00Z

cmake/sysbuild/bootloader_vars_preparation.cmake

as above, just read the dts directly from an image and do not use generator expressions (so the whole file can go)

I agree with removing generator expressions - done.

However with the file itself I'd like to leave most of it - I've now changed the name to bootloader_dts_utils.cmake

There are two things this file achieves:

I've now added functions nsib_get_s0_address, nsib_get_s1_address and nsib_get_provision_address. This, in case of S0/S1 allows to provide an abstraction layer, thanks to which other files does need to duplicate the code related to the fact that depending on the bootloader configuration (mcuboot present or not) the S0/S1 labels can be either boot_partition/boot_partition_slot1 or slot0_partition/slot1_partition

It provides validation (I've now wrapped it in the verify_bootloader_dts_configuration) function, which allows to verify that the appropriate partitions are used - for example verifies that zephyr,code-partition for mcuboot is set to boot_partition - and other similar checks. Almost all of our team members ran into an issue in which due to a wrong overlay the images were linked to wrong partitions which led to strange errors.
So we think that having verbose error messages in such cases will greatly help the user.

nordicjm · 2025-05-13T14:27:38Z

cmake/sysbuild/image_signing.cmake

honestly, if not using partition manager, do not store this in the cache. The cache is needed for variable replacement, it's sticky/buggy, so let's avoid creating issues for users that are only present due to how PM works

Ok, changed

nordicjm · 2025-05-13T14:28:55Z

cmake/sysbuild/provision_hex.cmake

check for nrf54h20 soc Kconfig instead then allow if set, otherwise throw error (nrf54l, nrf52, etc. should all show error)

nordicjm · 2025-05-13T14:29:29Z

cmake/sysbuild/provision_hex.cmake

missing indent

nordicjm · 2025-05-13T14:31:00Z

cmake/sysbuild/sign.cmake

limit this to when PM is disabled, same with below

Is this really needed? CONFIG_ROM_START_OFFSET defaults to 0 if partition manager is enabled.

why do pointless calculations which aren't clear from the code where they are used?

nordicjm · 2025-05-13T14:31:51Z

cmake/sysbuild/sign.cmake

Suggested change

--start-offset ${${slot}_input_data_start_offset}

I don't quite understand the suggestion, the --start-offset argument is necessary, otherwise the hash would be calculated CONFIG_ROM_START_OFFSET times 0x0 at the start of the image, which is later filled by imgtool

with PM this is 0, so like above it's doing something pointless for something that doesn't need it, considering if the value is not supplied to the script it will default to 0

Copilot

Pull Request Overview

A proof-of-concept PR to support NSIB nRF54H20 without relying on the partition manager.

Introduces a new offset parameter for hashing and signature validation functions.
Updates CMake and source code to remove partition manager dependencies and use NSIB-specific addresses/constants.
Adjusts tests and CLI argument parsing accordingly.

Reviewed Changes

Copilot reviewed 19 out of 32 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
scripts/bootloader/validation_data.py	Adds input_data_offset parameter and adjusts validation logic.
scripts/bootloader/tests/validation_data_test.py	Updates tests to pass the new offset parameter.
scripts/bootloader/hash.py	Propagates a new start_offset parameter in hash calculation.
scripts/bootloader/do_sign.py	Updates signing functions to use a start_offset parameter.
samples/bootloader/src/main.c	Updates partition constants and includes for NSIB usage.
include/fw_info.h	Adjusts memory map offsets to reflect new NSIB configuration.
include/bl_storage.h	Replaces PM-based storage addresses with NSIB-based ones.

Files not reviewed (13)

cmake/sysbuild/b0_mcuboot_signing.cmake: Language not supported
cmake/sysbuild/bootloader_dts_utils.cmake: Language not supported
cmake/sysbuild/image_signing.cmake: Language not supported
cmake/sysbuild/provision_hex.cmake: Language not supported
cmake/sysbuild/secureboot_merge.cmake: Language not supported
cmake/sysbuild/sign.cmake: Language not supported
samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron.conf: Language not supported
samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron.overlay: Language not supported
samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron_mcuboot_b0.conf: Language not supported
samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron_mcuboot_b0.overlay: Language not supported
samples/bootloader/sysbuild/mcuboot_s1_image.overlay: Language not supported
samples/bootloader/sysbuild/s1_image.overlay: Language not supported
subsys/CMakeLists.txt: Language not supported

Comments suppressed due to low confidence (3)

scripts/bootloader/validation_data.py:42

[nitpick] Consider renaming the parameter from 'input_data_offset' to 'start_offset' to be consistent with similar parameters introduced in hash.py and do_sign.py.

def get_hash(self, input_hex: IntelHex, input_data_offset: int) -> bytes:

samples/bootloader/src/main.c:139

Verify that the new NSIB_B0_ADDRESS and NSIB_B0_SIZE macros are correctly defined and consistently used across the codebase.

int err = fprotect_area(NSIB_B0_ADDRESS, NSIB_B0_SIZE);

include/bl_storage.h:182

Ensure that NSIB_PROVISION_ADDRESS is consistently defined and that its usage correctly replaces the PM_PROVISION_ADDRESS in all related modules.

#define BL_STORAGE ((const volatile struct bl_storage_data *)(NSIB_PROVISION_ADDRESS))

sysbuild/CMakeLists.txt

subsys/fw_info/Kconfig

tomchy · 2025-05-15T10:15:09Z

subsys/bootloader/bl_storage/bl_storage.c

Could you add a JIRA ref here too?

samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron_mcuboot_b0.conf

samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron.conf

include/bl_partitions.h

Copilot

Pull Request Overview

This PR refactors partition handling to remove Partition Manager dependencies, adds device-tree–based partition definitions, adjusts firmware info offset computation, and introduces nRF54H20-specific board support.

Replace PM_* symbols with DT-based NSIB_* macros and add bl_partitions.h
Update FW_INFO_VECTOR_OFFSET logic to use CONFIG_ROM_START_OFFSET when PM is disabled
Add new board YAML and variant entry for nRF54H20 DK with MCUBOOT B0 support

Reviewed Changes

Copilot reviewed 24 out of 39 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
include/fw_info.h	Added branch for `CONFIG_ROM_START_OFFSET` when PM is disabled
include/bl_storage.h	Swapped PM include for `bl_partitions.h` and updated `BL_STORAGE`
include/bl_partitions.h	New DT- and PM-based NSIB_* partition address/size macros
boards/nordic/nrf54h20dk/*.yaml	Added new board definition for MCUBOOT B0 configuration
boards/nordic/nrf54h20dk/board.yml	Added `mcuboot/b0` variant qualifier

Files not reviewed (15)

CODEOWNERS: Language not supported
boards/nordic/nrf54h20dk/Kconfig.defconfig: Language not supported
boards/nordic/nrf54h20dk/Kconfig.nrf54h20dk: Language not supported
boards/nordic/nrf54h20dk/Kconfig.sysbuild: Language not supported
boards/nordic/nrf54h20dk/board.cmake: Language not supported
boards/nordic/nrf54h20dk/nrf54h20dk_nrf54h20-memory_map_iron_mcuboot_b0.dtsi: Language not supported
boards/nordic/nrf54h20dk/nrf54h20dk_nrf54h20_cpuapp_iron_mcuboot_b0.dts: Language not supported
boards/nordic/nrf54h20dk/nrf54h20dk_nrf54h20_cpuapp_iron_mcuboot_b0_defconfig: Language not supported
cmake/sysbuild/b0_mcuboot_signing.cmake: Language not supported
cmake/sysbuild/bootloader_dts_utils.cmake: Language not supported
cmake/sysbuild/image_signing.cmake: Language not supported
cmake/sysbuild/provision_hex.cmake: Language not supported
cmake/sysbuild/secureboot_merge.cmake: Language not supported
cmake/sysbuild/sign.cmake: Language not supported
samples/bootloader/boards/nrf54h20dk_nrf54h20_cpuapp_iron.conf: Language not supported

Comments suppressed due to low confidence (2)

include/bl_partitions.h:31

The macro SOC_NV_FLASH_NODE_B0 is not defined here; consider using DT_REG_SIZE(NSIB_B0_CONTAINER_NODE) to consistently reference the container node.

#define NSIB_B0_CONTAINER_SIZE DT_REG_SIZE(SOC_NV_FLASH_NODE_B0)

include/bl_partitions.h:42

In the DT-based branch, address macros for S0 and S1 (NSIB_S0_ADDRESS and NSIB_S1_ADDRESS) are missing, which will lead to undefined references when used elsewhere.

#define NSIB_S0_SIZE DT_REG_SIZE(DT_NODELABEL(s0_partition))

include/fw_info.h

nordicjm

changes OK but needs updating as per linked comment

nordicjm · 2025-05-23T10:25:28Z

cmake/sysbuild/bootloader_dts_utils.cmake

these all need changing #22462

nordicjm · 2025-05-27T09:25:50Z

sysbuild/secureboot.cmake

apply the image configuration script to it e.g.

set_target_properties(${IMAGE} PROPERTIES IMAGE_CONF_SCRIPT ${ZEPHYR_BASE}/share/sysbuild/image_configurations/BOOTLOADER_image_default.cmake )

nordicjm · 2025-05-27T09:27:25Z

boards/nordic/nrf54h20dk/Kconfig.sysbuild

I think this is fixed

nordicjm · 2025-05-27T09:27:33Z

boards/nordic/nrf54h20dk/board.cmake

Suggested change

nordicjm · 2025-05-27T09:28:11Z

include/bl_partitions.h

this makes no sense

Should be addressed by now

This commit introduces the changes needed for running the NSIB on nRF54H - currently when running an application-core only application. Note: the NSIB is still experimental, as OTP memory is not handled properly - MRAM is used instead. Signed-off-by: Artur Hadasz <[email protected]>

Added as an extension to the nrf54h20dk board. Signed-off-by: Artur Hadasz <[email protected]>

Added support for the nrf54h20dk/nrf54h20/cpuapp/iron/b0/mcuboot in the nordic secure bootloader. Signed-off-by: Artur Hadasz <[email protected]>

The support for the sample with the nrf54h20dk/nrf54h20/cpuapp/iron/b0/mcuboot board was added. Signed-off-by: Artur Hadasz <[email protected]>

ahasztag · 2025-05-28T07:46:50Z

Closing as NSIB won't be supported on nRF54H20

github-actions bot added manifest changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels May 13, 2025

NordicBuilder added manifest-mcuboot manifest-zephyr DNM labels May 13, 2025

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 2 times, most recently from 34d5709 to 5557ad0 Compare May 13, 2025 11:54

ahasztag marked this pull request as ready for review May 13, 2025 12:17

ahasztag requested a review from a team as a code owner May 13, 2025 12:17

ahasztag requested a review from a team May 13, 2025 12:17

ahasztag requested review from a team as code owners May 13, 2025 12:17

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 3 times, most recently from 320daae to 883abbb Compare May 13, 2025 14:22

nordicjm requested changes May 13, 2025

View reviewed changes

ahasztag requested review from a team and adsz-nordic May 14, 2025 12:43

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 3 times, most recently from 7b3ff2e to 05782b9 Compare May 14, 2025 13:44

ahasztag requested a review from Copilot May 14, 2025 14:16

Copilot AI reviewed May 14, 2025

View reviewed changes

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch from 05782b9 to f58ba62 Compare May 15, 2025 09:02

tomchy reviewed May 15, 2025

View reviewed changes

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch from f58ba62 to 05784c7 Compare May 15, 2025 11:33

NordicBuilder added the DNM label May 20, 2025

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 2 times, most recently from 4c2034e to 7b19d1a Compare May 20, 2025 12:11

tomchy approved these changes May 21, 2025

View reviewed changes

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 3 times, most recently from b9d3bd4 to ddda2df Compare May 23, 2025 09:26

ahasztag requested review from Copilot and nordicjm May 23, 2025 10:05

Copilot AI reviewed May 23, 2025

View reviewed changes

include/fw_info.h Outdated

This comment was marked as spam.

Sign in to view

nordicjm reviewed May 23, 2025

View reviewed changes

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 5 times, most recently from 15b2aca to 3035b23 Compare May 27, 2025 07:03

nordicjm reviewed May 27, 2025

View reviewed changes

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch 2 times, most recently from 6ecff1e to ceee67b Compare May 27, 2025 12:20

ahasztag requested a review from nordicjm May 27, 2025 12:32

ahasztag added 4 commits May 27, 2025 15:39

boards: Added nrf54h20dk/nrf54h20/cpuapp/iron/b0/mcuboot variant

9001d21

Added as an extension to the nrf54h20dk board. Signed-off-by: Artur Hadasz <[email protected]>

bootloader: nrf54h20dk/nrf54h20/cpuapp/iron/b0/mcuboot support

54d9b23

Added support for the nrf54h20dk/nrf54h20/cpuapp/iron/b0/mcuboot in the nordic secure bootloader. Signed-off-by: Artur Hadasz <[email protected]>

samples: smp_svr: Extended zephyr sample for nrf54H20 + NSIB

f528302

The support for the sample with the nrf54h20dk/nrf54h20/cpuapp/iron/b0/mcuboot board was added. Signed-off-by: Artur Hadasz <[email protected]>

ahasztag force-pushed the NCSDK-33104_b0_lillium_poc branch from ceee67b to f528302 Compare May 27, 2025 13:39

ahasztag closed this May 28, 2025

NSIB nRF54H20 support - no partition manager #22274

NSIB nRF54H20 support - no partition manager #22274

Uh oh!

Conversation

ahasztag commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NordicBuilder commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NordicBuilder commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CI Information

Inputs:

Sources:

Github labels

Outputs:

Toolchain

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

Uh oh!

github-actions bot commented May 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

This comment was marked as spam.

Uh oh!

nordicjm left a comment

ahasztag commented May 13, 2025 •

edited

Loading

NordicBuilder commented May 13, 2025 •

edited

Loading

NordicBuilder commented May 13, 2025 •

edited

Loading