No merged.hex file when using ncs v3.3.0 without partition manager

[Chris__H]

Hello everyone,

I’m currently porting my old projects from NCS version 2.9.0 to 3.3.0.

In doing so, I no longer want to use the outdated Partition Manager; instead, I want to use Zephyr’s default device tree-based memory partitioning.

I converted my project following these instructions and successfully built it.

However, I am now missing the merged.hex and merged_CPUNET.hex files, which combine the bootloader and the application code. I need these files for our production to perform the “initial” programming of the devices.

Is it possible that the current toolchain (v3.3.0) doesn't yet support the merge process?

I also tried the conversion using a new/empty project from DevAcademy (l9/e5)—with the same result.

[BertL]

You have to add this config to your sysbuild.conf:

SB_CONFIG_MERGED_HEX_FILES=y

[Achim Kraus]

That results in with NCS 3.4.0:

"../merged_nrf9160dk_0_14_0_nrf9160.hex"

is there a way to go back to "merged.hex"?

Edited:

Even worser, I don't see the "merged.hex" from before, there are now two 

merged_nrf9160dk_0_14_0_nrf9160_ns.hex

merged_nrf9160dk_0_14_0_nrf9160.hex

I guess, it's now intended to have them merged by the customer ...