MCUBoot firmware loader update for NCS by ahasztag · Pull Request #27518 · nrfconnect/sdk-nrf

ahasztag · 2026-03-13T08:14:38Z

This PR adds support for FW loader updates, using a dedicated installer application. The idea of the installer application is similar to the installer application from nrf-bm (copy the attached FW loader to the target location) but the differences are significant (see attached table):

NordicBuilder · 2026-03-13T08:18:53Z

CI Information

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

Inputs:

Sources:

sdk-nrf: PR head: 7b34a697cfd07b9286ba8e1f6c4f084d0f6ddd78

more details

sdk-nrf:

PR head: 7b34a697cfd07b9286ba8e1f6c4f084d0f6ddd78
merge base: 97b2fe53568ada2a09d5ac755b26f72cc39ae046
target head (main): 950d004eebe7cf7b443dec2bfa60696974259934
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 (16)

CODEOWNERS
applications
│  ├── installer
│  │  ├── CMakeLists.txt
│  │  ├── Kconfig
│  │  ├── README.rst
│  │  ├── prj.conf
│  │  ├── socs
│  │  │  │ nrf54h20_cpuapp.conf
│  │  ├── src
│  │  │  │ main.c
│  │  │ sysbuild.conf
cmake
│  ├── sysbuild
│  │  │ image_signing_installer.cmake
doc
│  ├── nrf
│  │  ├── app_dev
│  │  │  ├── bootloaders_dfu
│  │  │  │  ├── mcuboot_nsib
│  │  │  │  │  │ bootloader_adding_sysbuild.rst
│  │  │  ├── device_guides
│  │  │  │  ├── nrf54h
│  │  │  │  │  │ ug_nrf54h20_partitioning_merged.rst
│  │  ├── applications.rst
│  │  ├── releases_and_maturity
│  │  │  ├── releases
│  │  │  │  │ release-notes-changelog.rst
sysbuild
│  ├── CMakeLists.txt
│  ├── Kconfig.firmware_loader
│  │ firmware_loader_installer.cmake

Outputs:

Toolchain

Version: 911f4c5c26
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:911f4c5c26_5ea73affbf

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

◻️ Toolchain - Skipped: existing toolchain is used
✅ Build twister - Skipped: Skipping Build & Test as it succeeded in a previous run: 42
✅ Integration tests
- ✅ test-sdk-audio - Skipped: Job was skipped as it succeeded in a previous run
- ✅ desktop52_verification - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-apps - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test_ble_nrf_config - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-ble_mesh - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-chip
- ✅ test-fw-nrfconnect-nfc - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf-iot_libmodem-nrf - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf-iot_zephyr_lwm2m - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf-iot_samples - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf-iot_lwm2m - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf-iot_thingy91 - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf_crypto - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-rpc - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-rs - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-fem - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-tfm - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-thread-main - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-sdk-find-my - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf_lrcs_mosh - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-nrf_lrcs_positioning - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-sdk-wifi - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-low-level - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-sdk-mcuboot - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-sdk-dfu - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-fw-nrfconnect-ps-main - Skipped: Job was skipped as it succeeded in a previous run
- ✅ test-secdom-samples-public - Skipped: Job was skipped as it succeeded in a previous run

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

github-actions · 2026-03-16T14:46:09Z

You can find the documentation preview for this PR here.

Preview links for modified nRF Connect SDK documents:

https://ncsbmdoc.z6.web.core.windows.net/ncs/PR-27518/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader_adding_sysbuild.html
https://ncsbmdoc.z6.web.core.windows.net/ncs/PR-27518/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_partitioning_merged.html
https://ncsbmdoc.z6.web.core.windows.net/ncs/PR-27518/nrf/applications.html
https://ncsbmdoc.z6.web.core.windows.net/ncs/PR-27518/nrf/releases_and_maturity/releases/release-notes-changelog.html
https://ncsbmdoc.z6.web.core.windows.net/ncs/PR-27518/nrf/applications/installer/README.html

nvlsianpu · 2026-03-16T10:53:04Z

+	int rc = 0;
+
+#if CONFIG_UNBOXER_FW_LOADER_ENTRANCE_SELF_INVALIDATE_BY_ERASE
+	rc = self_invalidate_by_erase(source_fa);


this rc value assignment requires separate check/log on error.

I actually think that it is not strictly necessary - there is already a log in self_invalidate_by_erase and we do treat this as a method of "requesting FW loader entrance", so the log below, although not perfect is not really wrong. I'd prefer to keep this as it is so that the code does not get more complicated with more ifdefs

nvlsianpu · 2026-03-16T14:23:11Z

+	}
+
+	off += fw_loader_tlv_info.it_tlv_tot;
+	*fw_loader_total_size = fw_loader_header.ih_hdr_size


calculating of that and the off is quite redundant. See not issue, just notice.

It is in fact a bit redundant, but I thought that explicitily writing what values sum to *fw_loader_total_size is more informative than off - *fw_loader_data_start_offset

nvlsianpu · 2026-03-16T14:49:36Z

+	uint32_t source_offset = fw_loader_data_start_offset;
+	uint32_t target_offset = 0;
+
+	rc = flash_area_flatten(target_fa, 0, flash_area_get_size(target_fa));


Actually it should avoid flatten on RRAM memory (this will reduces total lifetime endurance).
code can check flash_area device capability and perform erase if needed.

I've changed to flash_area_erase (also in self_invalidate_by_erase) - I did not find the capability you mentioned, but I assume all of the nordic devices support flash_area_erase so this does not really seem to be an issue

nvlsianpu · 2026-03-16T14:54:52Z

+		LOG_ERR("Failed to clear flash area");
+		return rc;
+	}
+	while (bytes_left > BUFFER_SIZE) {


you can heck whether flash_area_copy() will fit in instead of this code

Indeed, a much better solution, changed

Update: simply flash area copy was not enough, as the write alignment issue needed to be addressed. Please take a look now

nvlsianpu · 2026-03-16T16:10:47Z

+
+set(output ${CMAKE_BINARY_DIR}/fw_loader_unboxer.signed)
+
+add_custom_command(


just for consideration: produce also signed .hex (on Kconfig demand) for verification?

nordicjm · 2026-03-25T11:00:17Z

+CONFIG_LOG_MODE_IMMEDIATE=y
+CONFIG_LOG_MODE_MINIMAL=y


these 2 things clash, only one can be selected

Ok, left only CONFIG_LOG_MODE_IMMEDIATE

nordicjm · 2026-03-25T11:01:37Z

+  sysbuild_get(CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_REQ IMAGE ${installer_image}
+    VAR CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_REQ KCONFIG)


) goes on newline e.g.:

sysbuild_get(CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_REQ IMAGE ${installer_image} VAR CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_REQ KCONFIG )

Fixed in all instances in this file

nordicjm · 2026-03-25T11:03:04Z

+    sysbuild_get(mcuboot_CONFIG_BOOT_FIRMWARE_LOADER_BOOT_MODE IMAGE mcuboot
+      VAR CONFIG_BOOT_FIRMWARE_LOADER_BOOT_MODE KCONFIG)
+    if(NOT mcuboot_CONFIG_BOOT_FIRMWARE_LOADER_BOOT_MODE)
+      message(WARNING


rather than allowing these to mismatch, maybe a Kconfig should be added to sysbuild which sets it in the images?

Actually looking at this currently these warnings should not be in this file at all, as Kconfigs like CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_MODE are local to the application.

Removing this whole "configuration checks" part - the proper way to set the Kconfig-s is documented and errors are immediately detectable in runtime.

nordicjm · 2026-03-25T11:05:24Z

+  dt_partition_addr(code_addr PATH "${code_flash}" TARGET ${installer_image} REQUIRED)
+
+  math(EXPR start_offset_dts "${code_addr} - ${slot0_addr}")
+  if(start_offset_dts GREATER 0)
+    math(EXPR header_size "${header_size} + ${start_offset_dts}")
+    set(pad_header "--pad-header")
+  endif()
+


not following this, if pad header is needed then it should always be used, there shouldn't be a case of some things need it and some do not, that is the case with PM vs dts which is caused by PM but there is no PM here

The code can be a bit simplified here (removed the start_offset_dts GREATER 0) as the "header by DTS offset" should be always used with SB_CONFIG_MCUBOOT_SIGN_MERGED_BINARY - so if you meant the if(start_offset_dts GREATER 0) - removed the if.

The code is copied from sign_nrf54h20.cmake - this case is specifically for the nRF54H20 merged image firmware loader. In this case we do not use CONFIG_ROM_START_OFFSET for the header, instead we offset the cpuapp_slot0_partition from slot0_partition and use this space for the MCUBoot header, see for example here:

sdk-nrf/samples/dfu/ab/sysbuild/nrf54h20dk_nrf54h20_memory_map.dtsi

Line 34 in 59dc4df

cpuapp_slot0_partition: partition@800 {

Changing this approach would require the rework of the firmware loader merged image functionalities, which would be way out of scope of this PR.

nordicjm · 2026-03-25T11:08:08Z

    include(${ZEPHYR_NRF_MODULE_DIR}/cmake/sysbuild/mcuboot_nrf54h20.cmake)
  endif()

+  if(SB_CONFIG_FIRMWARE_LOADER_UPDATE_ENABLE)


-enable from the option name, that's what enabling a Kconfig implies

refactored (changed name to SB_CONFIG_FIRMWARE_LOADER_UPDATE)

tejlmand

Much better.

Small prompt proposals.
Only blocking prompt comments are the word Use, and missing help text.
Rest is just additional suggestions, but those are not blocking.

tejlmand · 2026-03-26T08:41:23Z

+	bool "Use boot mode"
+	depends on RETAINED_MEM
+	depends on RETENTION
+	depends on RETENTION_BOOT_MODE


why is there no help text ?

tejlmand · 2026-03-26T08:41:29Z

+	depends on RETAINED_MEM || SOC_NRF54H20
+	depends on RETENTION || SOC_NRF54H20
+	depends on NRF_MCUBOOT_BOOT_REQUEST
+	depends on IMG_MANAGER


why is there no help text ?

Indeed would be helpful, added

FrancescoSer · 2026-03-27T11:00:58Z

+* :kconfig:option:`SB_CONFIG_BOOTLOADER_MCUBOOT`
+* :kconfig:option:`SB_CONFIG_MCUBOOT_MODE_FIRMWARE_UPDATER`
+* :kconfig:option:`SB_CONFIG_FIRMWARE_LOADER_UPDATE`
+   This option selects :kconfig:option:`SB_CONFIG_FIRMWARE_LOADER_INSTALLER_BASIC` by default, which causes this application to be built.


Suggested change

This option selects :kconfig:option:`SB_CONFIG_FIRMWARE_LOADER_INSTALLER_BASIC` by default, which causes this application to be built.

This option selects :kconfig:option:`SB_CONFIG_FIRMWARE_LOADER_INSTALLER_BASIC` by default, which causes this application to be built.

nordicjm · 2026-03-27T11:32:36Z

+	depends on RETAINED_MEM
+	depends on RETENTION
+	depends on RETENTION_BOOT_MODE


surely it should just be RETENTION_BOOT_MODE since RETENTION_BOOT_MODE depends on RETENTION and RETENTION depends on RETAINED_MEM?

Leftover from a previous iteration when select was used, left only RETENTION_BOOT_MODE

nordicjm · 2026-03-27T11:34:01Z

+	depends on RETAINED_MEM || SOC_NRF54H20
+	depends on RETENTION || SOC_NRF54H20
+	depends on NRF_MCUBOOT_BOOT_REQUEST
+	depends on IMG_MANAGER


Suggested change

depends on RETAINED_MEM || SOC_NRF54H20

depends on RETENTION || SOC_NRF54H20

depends on NRF_MCUBOOT_BOOT_REQUEST

depends on IMG_MANAGER

depends on (RETENTION || SOC_NRF54H20) && NRF_MCUBOOT_BOOT_REQUEST && IMG_MANAGER

if I read it rightly?

Changed as suggested

nordicjm · 2026-03-27T11:43:21Z

+  generate_dfu_zip(
+    OUTPUT ${CMAKE_BINARY_DIR}/dfu_fw_loader_installer.zip
+    BIN_FILES ${output}.bin
+    TYPE application


type is application, trying to see what this means, seemingly in cmake/fw_zip.cmake it just passes it on to the script but scripts/bootloader/generate_zip.py doesn't even read it - what consumes this value and what does it do with it?

The python script for zip generation puts an additional field "type" in the manifest - the mobile app then uses it for differentiating it from the mcuboot update. As the installer upload currently behave exactly like a normal application upload from the mobile app-s perspective - the application type is used here.

nordicjm · 2026-03-27T11:44:09Z


 The project must also configure MCUboot to operate in firmware loader mode and specify a firmware loader image in the :file:`sysbuild.conf` file.
-For example to select ``smp_svr``, set the following options:
+For example, to select the ``ble_mcumgr`` firmware loader image, set the following options:


Is there documentation for this sample? If so, might want to link to that here

Added reference

nordicjm · 2026-03-27T11:46:12Z

+config FIRMWARE_LOADER_UPDATE
+	bool "Firmware loader update"
+	depends on MCUBOOT_MODE_FIRMWARE_UPDATER && !FIRMWARE_LOADER_IMAGE_NONE
+	help
+	  Firmware loader update.
+	  This will allow to update the firmware loader image with the help of the installer image.
+
+if FIRMWARE_LOADER_UPDATE
+
+choice FIRMWARE_LOADER_INSTALLER
+	prompt "Firmware loader installer image"
+	default FIRMWARE_LOADER_INSTALLER_BASIC
+
+config FIRMWARE_LOADER_INSTALLER_BASIC
+	bool "Basic fw loader installer"
+
+endchoice
+
+config FIRMWARE_LOADER_INSTALLER_IMAGE_NAME
+	string
+	default "installer" if FIRMWARE_LOADER_INSTALLER_BASIC
+
+config FIRMWARE_LOADER_INSTALLER_IMAGE_PATH
+	string
+	default "$(ZEPHYR_NRF_MODULE_DIR)/applications/installer" if FIRMWARE_LOADER_INSTALLER_BASIC


these things should all match the image name, so FIRMWARE_LOADER_INSTALLER_BASIC would mean installer_basic etc. easier to just rename to FIRMWARE_LOADER_INSTALLER

Ok, changed - I had to change the name of the choice itself (it used to be FIRMWARE_LOADER_INSTALLER, now it is FIRMWARE_LOADER_INSTALLER_APPLICATION) and changed the option name to FIRMWARE_LOADER_INSTALLER as suggested

FrancescoSer

Approving but please implement the previous suggestions

FrancescoSer · 2026-03-27T13:12:58Z

+The following are the DFU steps for updating the firmware loader image.
+
+.. figure:: ../images/dfu_steps_firmware_loader_update.svg
+   :alt: DFU operations for a firmware loader image update in MCUboot firmware-loader mode


This should probably be added as a separate task, as it needs new pictures to be created from scratch.

umapraseeda · 2026-03-27T14:56:13Z

 /applications/matter_weather_station/*.rst @nrfconnect/ncs-matter-doc
 /applications/nrf5340_audio/**/*.rst      @nrfconnect/ncs-audio-doc
 /applications/nrf_desktop/**/*.rst        @nrfconnect/ncs-si-xcake-doc
+/applications/installer/                  @nrfconnect/ncs-eris


Perhaps this could be moved up to line 39

umapraseeda · 2026-03-27T14:57:22Z


  * Added support for the nRF54H20 SoC.

+* Added support for firmware loader updates using the :ref:`installer` application.


Shouldn't we have this as a new application under Applications?

Added, I assume that if IPC radio is there this should be also here, although this is a helper application used specifically from the MCUBoot firmware loader update, so this is not really a separate entity - take a look if the added changelog entry is OK.

umapraseeda · 2026-03-30T06:19:57Z

@@ -0,0 +1,50 @@
+.. _installer:
+
+Installer


Should the name be more specific?

The "installer" name was used in the NCS baremetal and we were asked by PMT to used the same name - however, I've added "(MCUboot Firmware Loader installer)" in parentheses - this should make the purpose clearer

This commit adds support for FW loader updates, using a dedicated installer application. Signed-off-by: Artur Hadasz <artur.hadasz@nordicsemi.no>

NordicBuilder · 2026-03-30T08:52:21Z

Memory footprint analysis revealed the following potential issues

applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 9014[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 5770[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High RAM usage: 12662[B] - link (cc: @nrfconnect/ncs-ll-ursus)
applications.hpf.gpio.icbmsg[nrf54l15dk/nrf54l15/cpuflpr]: High ROM usage: 9410[B] - link (cc: @nrfconnect/ncs-ll-ursus)

Note: This message is automatically posted and updated by the CI (latest/sdk-nrf/PR-27518/42)

NordicBuilder added the doc-required PR must not be merged without tech writer approval. label Mar 13, 2026

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch 6 times, most recently from 3bba72b to 295728e Compare March 13, 2026 13:28

NordicBuilder added the changelog label Mar 13, 2026

michalek-no approved these changes Mar 16, 2026

View reviewed changes

ahasztag requested review from a team, adsz-nordic, de-nordic, nvlsianpu and tomchy March 16, 2026 12:50

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from 295728e to 08e1250 Compare March 16, 2026 14:10

nvlsianpu reviewed Mar 16, 2026

View reviewed changes

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from 08e1250 to 58a5899 Compare March 17, 2026 12:54

ahasztag changed the title ~~[DRAFT] Firmware loader update for NCS~~ MCUBoot firmware loader update for NCS Mar 17, 2026

ahasztag requested review from maciejpietras and nvlsianpu March 17, 2026 12:59

ahasztag marked this pull request as ready for review March 17, 2026 13:00

ahasztag requested review from a team and FrancescoSer as code owners March 17, 2026 13:00

nordicjm requested changes Mar 25, 2026

View reviewed changes

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch 3 times, most recently from 6ea15ae to 35dda0e Compare March 26, 2026 07:54

ahasztag requested a review from nordicjm March 26, 2026 07:54

tejlmand requested changes Mar 26, 2026

View reviewed changes

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from bb7ff4b to 914c2f7 Compare March 26, 2026 10:15

tejlmand approved these changes Mar 26, 2026

View reviewed changes

ahasztag added this to the 3.3.0 milestone Mar 27, 2026

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from 914c2f7 to 5b4f8ac Compare March 27, 2026 11:32

FrancescoSer requested changes Mar 27, 2026

View reviewed changes

nordicjm reviewed Mar 27, 2026

View reviewed changes

ahasztag requested a review from nordicjm March 27, 2026 12:48

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from 5b4f8ac to bdb78fb Compare March 27, 2026 12:49

FrancescoSer requested changes Mar 27, 2026

View reviewed changes

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch 2 times, most recently from b3de8bf to c27391c Compare March 27, 2026 13:05

FrancescoSer requested changes Mar 27, 2026

View reviewed changes

FrancescoSer approved these changes Mar 27, 2026

View reviewed changes

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from 3da9898 to debce80 Compare March 27, 2026 13:18

umapraseeda reviewed Mar 30, 2026

View reviewed changes

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from 524ea74 to cda75c5 Compare March 30, 2026 07:11

sysbuild: Add support for FW loader updates

7b34a69

This commit adds support for FW loader updates, using a dedicated installer application. Signed-off-by: Artur Hadasz <artur.hadasz@nordicsemi.no>

ahasztag force-pushed the NCSDK-37481_fw_loader_update branch from cda75c5 to 7b34a69 Compare March 30, 2026 07:17

nordicjm approved these changes Mar 30, 2026

View reviewed changes

umapraseeda approved these changes Mar 30, 2026

View reviewed changes

b-gent approved these changes Mar 30, 2026

View reviewed changes

tomchy merged commit 73b85a4 into nrfconnect:main Mar 30, 2026
21 checks passed

ahasztag deleted the NCSDK-37481_fw_loader_update branch May 4, 2026 07:10


		set(output ${CMAKE_BINARY_DIR}/fw_loader_unboxer.signed)

		add_custom_command(

		sysbuild_get(CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_REQ IMAGE ${installer_image}
		VAR CONFIG_INSTALLER_FW_LOADER_ENTRANCE_BOOT_REQ KCONFIG)

	This option selects :kconfig:option:`SB_CONFIG_FIRMWARE_LOADER_INSTALLER_BASIC` by default, which causes this application to be built.
	This option selects :kconfig:option:`SB_CONFIG_FIRMWARE_LOADER_INSTALLER_BASIC` by default, which causes this application to be built.


		* Added support for the nRF54H20 SoC.

		* Added support for firmware loader updates using the :ref:`installer` application.

		CONFIG_LOG_MODE_IMMEDIATE=y
		CONFIG_LOG_MODE_MINIMAL=y

Conversation

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

Uh oh!

Uh oh!

NordicBuilder commented Mar 13, 2026 • 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 Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tejlmand left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

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!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

ahasztag commented Mar 13, 2026 •

edited

Loading

NordicBuilder commented Mar 13, 2026 •

edited

Loading

github-actions Bot commented Mar 16, 2026 •

edited

Loading