NCS 3.4.0, compiling with ns option

RE: NCS 3.4.0, compiling with ns option

embeddedCoder — Tue, 04 Aug 2026 19:40:57 GMT

Linking to this ticket since it sounds like it could be similar:

devzone.nordicsemi.com/.../sdk-3-4-0-build-flash-issue

RE: NCS 3.4.0, compiling with ns option

Stefano Infante — Tue, 28 Jul 2026 14:54:49 GMT

Thanks Simon.

As my project is at a very early stage, I think I’ll wait for the NCS 3.4.0 update for now and, in the meantime, use the board without ns.

Best regards,

Stefano

RE: NCS 3.4.0, compiling with ns option

Simon D-M — Tue, 28 Jul 2026 13:38:51 GMT

Hi,

I actually wasn't able to replicate this issue on the nRF54L15, can you please register another ticket for your case. It seems to be a bit different.

Best regards,

Simon

RE: NCS 3.4.0, compiling with ns option

Simon D-M — Tue, 28 Jul 2026 13:34:12 GMT

Hi,

From my understanding, this is caused by the migration from "partition manager" to devicetree partitions that came with v3.4.0. In NCS, by default, MCUboot is disabled but currently the "MCUboot partition" is still in the default partition of the /ns chips. So, currently, if you want to build for a /ns chip, you have 2 solutions:

enable MCUboot by adding "SB_CONFIG_BOOTLOADER_MCUBOOT=y" to your sysbuild.conf

remove the MCUboot partition manually using an overlay file. Here is an example overlay file for the nRF9151 DK that I generated using AI:

/*
 * Remove MCUboot on nRF9151: TF-M secure image now starts at 0x0.
 * The secondary slot (slot1) is dropped since there is no bootloader/DFU.
 * SRAM (&sram0) is intentionally NOT modified — its split is defined by
 * the TrustZone secure/non-secure boundary and the modem shared memory,
 * neither of which depend on MCUboot.
 */

/delete-node/ &boot_partition;
/delete-node/ &slot0_partition;   /* also deletes slot0_s / slot0_ns children */
/delete-node/ &slot1_partition;   /* also deletes slot1_s / slot1_ns children */

&flash0 {
	partitions {
		/* Primary (and only) image area, now based at 0x0 */
		slot0_partition: partition@0 {
			compatible = "zephyr,mapped-partition";
			label = "image-0";
			reg = <0x00000000 0x70000>;      /* 448 KB */
			ranges = <0x0 0x0 0x70000>;
			#address-cells = <1>;
			#size-cells = <1>;

			slot0_s_partition: partition@0 {
				compatible = "zephyr,mapped-partition";
				label = "image-0-secure";
				reg = <0x00000000 0x40000>;   /* 256 KB TF-M secure */
			};

			slot0_ns_partition: partition@40000 {
				compatible = "zephyr,mapped-partition";
				label = "image-0-nonsecure";
				reg = <0x00040000 0x30000>;   /* 192 KB non-secure app */
			};
		};

		/*
		 * tfm_ps / tfm_its / tfm_otp / storage remain untouched
		 * at 0xf0000..0x100000 (defined in the base partition.dtsi).
		 */
	};
};

The nRF Connect SDK team is working on it. And, I believe it will be fixed soon in a next NCS revision.

Best regards,

Simon

RE: NCS 3.4.0, compiling with ns option

Stefano Infante — Tue, 28 Jul 2026 08:58:07 GMT

I tried west build -p always with the ns board, I completely erased my board's flash and reflashed it. Unfortunately nothing changed.

I will wait for someone from Nordic to reply. Thanks

RE: NCS 3.4.0, compiling with ns option

Ingfu — Mon, 27 Jul 2026 11:01:19 GMT

We have a similar issue with the nrf54l15. Our application works with v3.3.1 with tf-m but not on 3.4.0 with tf-m. On 3.4.0 only as cpuapp works without tf-m. I believe, 3.4.0 broke tf-m.